SAP FICO Mass Posting from Excel: Pick the Right Transaction

Which transaction for which job

In PostNow.ai each row is posted through the BAPI shown, so the choice you make here decides which template you download or build. What appears on the lines decides the transaction, not the size of the file.

Four questions route almost any finance file, and the order matters. Is there a purchase order behind it? Then it is MIRO, because an invoice posted in FB60 against an order leaves the PO history without the invoice and the GR/IR account uncleared. Is there a vendor or customer on the line? Then FB60 or FB70. Do you need to choose posting keys yourself? Then FB01. Do the cost objects the lines reference already exist? If not, the file is not ready, whatever the transaction.

Asset postings from Excel, and where the asset master fits

PostNow.ai posts asset acquisitions through BAPI_ASSET_ACQUISITION_POST, the BAPI behind ABZON (acquisition with automatic offsetting entry); the free ABZON asset acquisition template has one row per acquisition. The asset must already exist: creating asset masters in bulk (AS01) is a separate job covered in mass create assets in SAP (AS01).

• Use the asset BAPI, not the accounting one. BAPI_ACC_DOCUMENT_POST carries an asset number but no asset transaction type, so it is the wrong route for an acquisition. BAPI_ASSET_ACQUISITION_POST takes the transaction type (100 for an external acquisition) and the offsetting account.
• The asset value date drives depreciation, not the posting date. A wrong value date shifts the depreciation start without any error message.
• Retirements and transfers have their own BAPIs. SAP's asset accounting documentation lists BAPI_ASSET_RETIREMENT_POST for retirements (the ABAVN scrapping case, for example) and BAPI_ASSET_TRANSFER_POST for transfers, each with a matching _CHECK function. Pick them in PostNow.ai's BAPI search and prove them on a few assets in a test client before a full run.
• Check every depreciation area after the pilot. SAP KBA 3716976 (S/4HANA) describes AAPO 704 "Depreciation area xx is a parallel area; it cannot be selected", where the BAPI posts the leading area but not the parallel one. Open a pilot asset in the Asset Explorer (AW01N) and confirm the values in each area before the full run.

Period control: OB52 and the MM period

PostNow.ai's Simulate returns SAP's period check on every row, but the fix for a closed period sits with whoever owns the close calendar. Two calendars are involved, and backdated files usually fail on the one nobody checked.

• The FI posting period is opened and closed in OB52 per posting period variant and account type (+ all, A assets, D customers, K vendors, M materials, S G/L accounts). A closed period returns F5 201 "Posting period … is not open".
• The MM period is a separate calendar, moved forward with MMPV; MMRV shows the current period and whether postings to the previous one are allowed. A pure G/L journal ignores it; a MIRO invoice or a goods movement needs both.
• The posting date is a decision, not a default. A =TODAY() formula posts October's accruals into November the moment the run slips past midnight. Type the date, or derive it from a period cell finance owns.

Month-end close postings from Excel

PostNow.ai fits the month-end postings whose amounts are calculated in Excel each period: the model produces this month's figures and the same published template posts them. Postings with fixed amounts or fixed reversal dates are often better left to SAP's own tools.

Run the files before the busiest close day, not during it: anything with known values can post early, and a run posted on the last open day leaves no room to reverse and re-post if the pilot shows a problem. After period-end postings, check the result in a financial statement (balance sheet and P&L) in Excel, built from G/L balances by account and split into balance sheet and P&L accounts.

Tax, currency and rounding: what breaks balance

PostNow.ai sends the amounts as the sheet holds them, so a file that balances in Excel can still fail SAP's balance check in Simulate. Three causes account for most of it.

• The tax line. BAPI_ACC_DOCUMENT_POST has no counterpart to the "Calculate tax" checkbox on the FB60 and FB70 screens: tax is a line of its own in ACCOUNTTAX, with the tax amount and base amount in CURRENCYAMOUNT. A gross vendor or customer amount with net lines and no tax line does not balance. Prove one tax-relevant document on Simulate before the full file.
• Foreign currency. A document in a currency other than the company code currency balances in document currency; SAP translates with the rate valid on the translation date, or with an exchange rate you pass. If no rate is maintained for that currency pair and date, the document fails, so load the OB08 rates first.
• Rounding in allocations. A total split by percentage and rounded per receiver can miss by 0.01. Put the difference on the last line with a formula (total minus the sum of the others), so every document still sums to zero.

When a run goes wrong: reversal, adjustment, compensation

PostNow.ai reverses documents in bulk from a file: the free FB08 reversal template on BAPI_ACC_DOCUMENT_REV_POST, one row per document, or a recorded FB08. Which kind of correction is right is a finance decision, so agree it before the first production run.

• Reversal cancels the whole document. FB08 reverses one, F.80 a selection; the document numbers the run wrote back are the selection. The reversal BAPI identifies the original by object type and key (BKPF-AWTYP, AWKEY), not by document number. Several SAP Community answers report it refusing journals posted through the accounting BAPI while others report it working, so reverse a few in a test client first; a recorded FB08 or F.80 does the same job.
• MIRO invoices are reversed with MR8M, not FB08; see MIRO mass invoice posting.
• Adjustment posts a correcting entry when only some lines were wrong; the original stays valid.
• Compensation in a later period is often the only route once the original period is closed: a reversal reason that allows a different posting date, or a new journal with flipped signs.
• Cleared items stop a reversal. If a vendor or customer line has been paid or cleared, SAP refuses with "Document already contains cleared items - reversal not possible" until the clearing is reset.
• Size runs so they can be reversed. Split by company code or journal type; a run that would take an afternoon to reverse should have been two runs.

What S/4HANA changes for finance mass posting

PostNow.ai uses the same finance templates on S/4HANA: BAPI_ACC_DOCUMENT_POST, BAPI_INCOMINGINVOICE_CREATE and the asset BAPIs are all there, so a template proven on ECC usually needs new field values, not a new structure.

• One line item table. The universal journal keeps FI and CO line items together in ACDOCA instead of separate ledger tables. Reconciliation reports built on old ledger tables need a check; the posting run does not change.
• Profit center on every line. Many S/4HANA systems require a profit center on each line, and the segment is usually derived from it; add the column even where ECC derived it later.
• Customers and vendors are business partners. FB60 and FB70 still post to the customer or vendor number, which must exist with its company code data; see SAP business partner automation.
• New asset accounting. SAP's documentation for New Asset Accounting lists the asset posting BAPIs with accounting principle, ledger group and depreciation area fields. Check every area of a pilot asset after the first run.
• API mode. PostNow.ai can also post journals through SAP's SOAP service Journal Entry - Post (Synchronous), with its test-run flag used for Simulate.

What to plan for in finance mass posting

PostNow.ai posts through SAP's own BAPIs, so SAP's balance, period, account and CO checks decide every result.

• Run SAP's checks in Simulate. Validate checks formats, lengths and allowed values in Excel; balance, period and account checks start when Simulate calls SAP.
• Post as named users. Each user posts with their own SAP login and authorisations. For recorded transactions, PostNow.ai logs in to SAP GUI only on the user's own computer, with the user's own stored login, when the user starts the action (Record, Run, Debug or Call Transaction); never on a server, never unattended, never with someone else's login.
• Approve the file, not the run. With an approval policy on the template, the approver releases the exact data; a file changed after approval needs a new approval.
• Keep re-runs in the same workbook. The re-post check reads this sheet's Run Log, so a copied file with the same documents starts without one.
• Name an owner per template. When the chart of accounts or a document type changes, someone re-proves the template on Simulate before the next close.
• Reconcile every run against the source model the same day, while the run is fresh.

Frequently asked questions