FB60 Tcode in SAP: How to post a Purchase Invoice

โšก Smart Summary

Posting a purchase invoice in SAP uses transaction FB60, the Financial Accounting entry point for supplier invoices that carry no purchase order reference, covering local currency, foreign currency, tax codes and payment terms.

  • ๐Ÿ”˜ Transaction FB60: Posts supplier invoices in Financial Accounting without any purchase order or goods receipt reference.
  • โ˜‘๏ธ Header data: Vendor ID, invoice date, posting date, amount, tax code and the Calculate Tax indicator drive the header entry.
  • โœ… Item details: Each expense or purchase G/L account line is debited while the vendor reconciliation account is credited automatically.
  • ๐Ÿงช Balance check: A zero balance and a green status light confirm the document is complete before posting.
  • ๐ŸŒ Foreign currency: The Local Currency tab allows the exchange rate and translation date to be overridden for document currency invoices.
  • ๐Ÿ› ๏ธ Troubleshooting: Missing tax base amounts, blocked vendors and absent cost centre assignments cause most FB60 posting failures.

FB60 in SAP: How to Post a Purchase Invoice

FB60 is the Financial Accounting transaction used to enter a supplier invoice directly, without a purchase order or a goods receipt behind it. The walkthrough below covers a domestic invoice first, then the same transaction used for a document posted in a foreign currency.

How to Post a Purchase Invoice in SAP Using FB60

Step 1) Enter transaction FB60 in the SAP command field, as shown in the screenshot below.

SAP Easy Access screen with transaction code FB60 typed into the command field

Step 2) In the next screen, enter the company code you want to post the invoice to. The pop-up below appears the first time FB60 is opened in a session.

FB60 Enter Company Code pop-up used to set the company code for the vendor invoice

Step 3) In the next screen, enter the following header data. The Basic data tab in the image that follows shows where each field sits.

  1. Enter the Vendor ID of the vendor to be invoiced
  2. Enter the Invoice Date
  3. Enter the Amount for the invoice
  4. Select the Tax Code for the tax applicable
  5. Select the tax indicator “Calculate Tax”

FB60 Basic data tab showing vendor ID, invoice date, amount, tax code and the Calculate Tax indicator

Step 4) Check the payment terms on the Payment tab page. The baseline date and terms of payment shown here decide when the item becomes due.

FB60 Payment tab displaying baseline date and payment terms for the supplier invoice

Step 5) In the item details section, enter the following. The grid below is where the offsetting expense line is captured.

  1. Enter the Purchase account
  2. Select Debit
  3. Enter the Amount for the invoice
  4. Check the Tax code

FB60 item details grid with the purchase G/L account, debit posting key, amount and tax code

Step 6) After completing the above entries, check the status of the document. A zero balance and a green traffic light, as in the strip below, mean the document is ready.

FB60 status line showing a zero balance and a green traffic light before posting

Step 7) Press the Post button in the standard bar, highlighted below.

Post button on the SAP standard toolbar used to save the FB60 vendor invoice

Step 8) Wait for the document number to be generated and displayed on the status bar for confirmation, as shown here.

SAP status bar confirming the vendor invoice document number after posting in FB60

The purchase invoice has now been posted successfully, and the open item appears against the vendor account.

How to Post a Foreign Currency Vendor Invoice in FB60

The same transaction handles invoices received in a currency other than the company code currency. Only the currency and exchange rate handling differ from the steps above.

Step 1) Enter transaction code FB60 in the SAP command field. The entry screen opens as pictured below.

FB60 initial screen opened for a foreign currency vendor invoice

Step 2) In the next screen, enter the following data. Each entry maps to the header and item fields visible in the following image.

  1. Enter the Vendor ID of the vendor whose invoice is to be posted
  2. Enter the Invoice Date
  3. Enter the Document Type as Vendor Invoice
  4. Enter the invoice amount in the currency in which the invoice is to be posted (document currency)
  5. Enter the Tax Code applicable to the invoice
  6. Enter the purchase G/L account to be debited
  7. Enter the Debit Amount

FB60 header and item entry for a foreign currency invoice with document currency and purchase G/L account

Step 3) The exchange rate can be adjusted on the Local Currency tab, shown below.

FB60 Local Currency tab where the exchange rate and translation date can be adjusted

Step 4) After maintaining the exchange rate, press Save to post the document using the toolbar icon below.

Save icon on the SAP toolbar used to post the foreign currency vendor invoice

Step 5) Check the status bar for the document number generated, as confirmed in the message below.

SAP status bar showing the document number generated for the foreign currency vendor invoice

Key Fields and Document Types in FB60

Several FB60 fields are easy to confuse because they look similar but drive different postings. The table below explains what each one controls.

Field What it controls
Invoice Date The date printed on the supplier document. It normally drives the baseline date used for payment terms.
Posting Date The date the entry hits the ledger, and therefore the posting period and fiscal year of the document.
Reference The external invoice number. It is the field the duplicate invoice check compares against existing documents.
Document Type KR for a standard vendor invoice, KG for a vendor credit memo, and KZ for a vendor payment. The type controls the number range.
Calculate Tax When ticked, the system derives the tax amount from the tax code instead of expecting it to be keyed manually.
Payment Terms Copied from the vendor master but changeable per document. It sets the due date and any cash discount.

Only one vendor line is permitted per FB60 document. Invoices that must split across two suppliers, or that need several vendor lines, are entered with the general document entry transactions FB01 or F-43 instead.

FB60 vs MIRO: When to Use Each Transaction

New users often post an invoice in the wrong place. The distinction is simply whether a purchase order sits behind the document.

Aspect FB60 MIRO
Module Financial Accounting (FI) Materials Management (MM), logistics invoice verification
Purchase order Not required โ€” no PO reference Mandatory โ€” invoice is matched to a PO
Goods receipt Not involved Three-way match against the goods receipt
Typical use Rent, utilities, telephone, audit fees, stationery Trade payables for materials and services procured on a PO
Accounts updated Vendor and expense or purchase G/L accounts GR/IR clearing, material or stock accounts, price differences, vendor

Where the Materials Management module is not implemented, or where the spend never passes through purchasing, FB60 is the correct entry point. Anything raised on a purchase order should be verified through MIRO so the GR/IR clearing account balances.

Common FB60 Errors and Related T-codes

Most FB60 failures come from missing derivation data rather than from the transaction itself. The problems below account for the majority of posting errors.

  • “Enter tax base amount for account โ€ฆ in company code”: the tax code expects a base amount. Tick Calculate Tax, or key the tax figure on the item line.
  • Account requires an assignment to a CO object: the expense account is cost element managed. Open the line item and enter a cost centre, internal order or WBS element.
  • Posting period not open: the posting date falls outside the open period. Correct the date, or have the period opened in OB52.
  • Vendor blocked for posting: a posting block is set on the supplier master. Review it in FK02 or XK02 before retrying.
  • Duplicate invoice warning: the same reference, amount and date already exist. Confirm the document is genuinely new before overriding the message.

The transactions listed below are the ones most often needed alongside FB60.

T-code Purpose
FV60 Park a supplier invoice for later completion and approval
FBV0 Post or delete a parked vendor document
FB65 Post a vendor credit memo for a purchase return
FB08 Reverse an incorrectly posted document
FBL1N Display vendor line items and open invoices
F-53 Post an outgoing payment against the invoice
OB08 Maintain the exchange rates used for foreign currency documents

Checking the vendor line items in FBL1N straight after posting is the quickest way to confirm that the invoice reached accounts payable with the expected due date and amount.

FAQs

Yes. Transaction FV60 parks a supplier invoice so that data is held without updating transaction figures. A reviewer then completes and posts it with FBV0. Parking suits invoices awaiting a cost centre, an approval or a missing tax base amount.

FB60 debits the expense or purchase G/L account entered in the item details and credits the vendor reconciliation account derived from the supplier master. Tax lines post automatically to the input tax account when the Calculate Tax indicator is set.

Use FB08 for a single document or F.80 for a mass reversal. Enter the document number, company code, fiscal year and a reversal reason. Cleared documents must first be reset with FBRA before FB08 accepts them.

The system reads exchange rate type M from table TCURR, maintained in transaction OB08, using the translation date. Typing a rate directly on the Local Currency tab overrides that default for the single document only.

No. FB60 accepts exactly one vendor line per document. Splitting an amount across several suppliers, or posting two vendor lines together, requires the general document entry transactions FB01 or F-43 instead.

Machine learning models read scanned supplier documents, predict the G/L account and cost centre, and score duplicate or fraudulent invoices before entry. SAP delivers this through Document Information Extraction and the Business AI capabilities embedded in accounts payable.

GitHub Copilot accelerates the code around the transaction rather than the SAP screen. It drafts ABAP wrappers for BAPI_ACC_DOCUMENT_POST, batch input recordings and OData payloads that an agentic pipeline runs. Generated postings still need functional testing in a sandbox client.

Yes. FB60 runs in S/4HANA as the Create Incoming Invoices app. SAP also ships the Fiori app Create Supplier Invoice (F0859), which supports parking and attachments. Public cloud editions expose the Fiori apps rather than the classic GUI transaction.

Summarize this post with: