How to Reconcile Export Payments in SAP? A Complete Guide

Post the shortfall as a bank charge expense using FB50 when the SWIFT credit arrives short of the invoice amount because of correspondent bank deductions. Do not write it off against the customer invoice, so the original invoice amount remains intact for shipping bill and GSTR-1 matching. Use the clearing account entry to split the incoming bank credit into two lines: the full invoice amount applied to the customer open item, and the bank charge deducted posted to the expense account.

SAP does not have a dedicated standard field for FIRC or e-BRC reference numbers out of the box. Exporters typically store this reference in the Assignment field or a custom text field in the payment document, and you can use transaction FB02 to edit the document after posting. Record the FIRC reference against the cleared customer document so it can be retrieved during RBI reporting or bank audits. Without this linkage, the SAP entry and the compliance record exist as two disconnected items.

Use transaction F-28 (incoming payment posting) and select multiple open items from the customer account to apply the single remittance amount across several export invoices. SAP clears each selected line item partially or fully depending on the amounts. Post any residual difference left after all selected invoices are cleared to a clearing or suspense account, and resolve it once the buyer confirms the allocation.

SAP does not enforce FEMA realization deadlines natively. Exporters typically use the open item aging report via FBL5N, filtering by document date, to identify export invoices whose payment has not been received within the FEMA-stipulated period. A custom aging bucket or a periodic report exported from FBL5N to Excel is the most common approach. You then follow up with the overseas buyer or the bank's EDPMS record to confirm realization status.

Post each cause of the mismatch separately, because the difference can arise from correspondent bank charges, exchange rate differences, or partial payments. Do not make a single adjustment to the shipping bill value. For compliance purposes, the shipping bill value must remain unchanged, and all differences are absorbed through bank charge postings, FX gain/loss entries, or credit notes raised against the buyer.

Post an advance received from an overseas buyer before shipment as a credit to a customer advance account, and do not post it directly to the revenue account. Use transaction F-29 or F-02, which creates a noted item or a special G/L entry against the customer. Once the export invoice is raised and the shipment is completed, clear the advance against the invoice using F-32, netting the advance amount against the outstanding receivable.

Yes. An EEFC account holds foreign currency without immediate conversion to INR, so it requires its own house bank and bank account master data in SAP (transaction FI12). This keeps foreign currency balances tracked separately from INR accounts. Post transactions flowing through the EEFC account in the original foreign currency so that SAP can apply the correct exchange rate when the funds are eventually converted or used for import payments.

A mismatch between the SAP ledger balance and the e-BRC value typically occurs when exchange rate differences, bank charges, or partial payments have not been correctly posted in SAP. The e-BRC reflects the actual foreign inward remittance amount, while SAP may still show the original invoice value as the open item. To audit it, compare the cleared customer line items in FBL5N against the e-BRC amount and date. Any residual difference should trace back to an unposted FX gain/loss or an omitted bank charge entry.