How FB60 Vendor Invoice Posting Works
The FB60 process begins with an approved supplier invoice and the accounting information required to recognize the obligation. The accounting clerk enters the vendor account and invoice header information, then assigns the expense, asset, or other appropriate offsetting account. SAP validates required fields and applies configured company-code, tax, currency, and payment rules.
The process is particularly relevant to invoice processing because FB60 converts an external supplier document into a structured accounting transaction. Modern workflows can support AP Automation Software by extracting invoice information, validating fields, determining coding, and routing the transaction for review before the accounting document is posted in SAP ECC.
- Identify the correct vendor and company code.
- Enter invoice and posting dates, amount, currency, and reference information.
- Assign the appropriate expense, asset, or other offsetting account.
- Enter applicable tax codes and required cost assignments.
- Review the document balance and supporting information.
- Post the vendor invoice and generate the SAP accounting document.
Key Data Elements in FB60
Accurate FB60 posting depends on the quality of both invoice information and accounting assignments. Header data normally includes the vendor, document date, posting date, invoice amount, currency, reference, and applicable payment terms. Line-item data identifies the account being debited and may include cost center, internal order, profit center, business area, tax code, or asset information.
For non-PO invoices, accounting judgment is especially important because the transaction may not have a purchase order or goods receipt providing the coding structure. procurement policies can nevertheless establish approval requirements and purchasing controls for invoices that originate outside a purchase-order workflow.
Supplier information also affects posting quality. Effective vendor management helps maintain accurate vendor master records, payment details, tax information, and communication channels that support reliable invoice processing.
FB60 Compared With MIRO
FB60 and MIRO both support vendor invoice accounting, but they serve different transaction patterns. MIRO is closely associated with purchase-order-based invoice verification, where the invoice can be evaluated against purchasing and goods-receipt information. FB60 is designed for direct FI invoice entry, making it useful when there is no purchase order reference.
For FB60 workflows, invoice capture can extract supplier name, invoice number, dates, amounts, taxes, and other fields from incoming documents. The extracted information can then be validated and used for accounting-code determination. invoice matching may still be applied where contracts, receipts, purchase records, or other supporting information are available, even when a traditional PO-based three-way match is not used.
Detailed workflow guidance such as Vendor Invoice Processing 2025: AI Supplier Workflow Guide can help finance teams evaluate how capture, validation, matching, coding, approval, and posting fit together around vendor invoices. How Vendor Portals Improve Invoice Transparency is also relevant when supplier-facing visibility is used to communicate invoice status throughout capture, validation, approval, and posting stages.
Accounting and Payment Impact
When an FB60 document is posted, SAP ECC records the vendor liability and the corresponding expense, asset, tax, or other account assignment. The resulting accounting document becomes part of the company's financial records and provides the basis for subsequent settlement.
For example, if a company records a $12,500 consulting invoice excluding applicable tax, the expense account is debited for the appropriate amount while the vendor account is credited for the total payable. The exact entries depend on tax configuration and the transaction's accounting requirements.
After posting, payments can be scheduled according to the vendor's payment terms and the company's payment process. Payment Approval represents the control step through which an authorized person confirms that a payable can proceed toward settlement. Invoice-related controls can also use Invoice Matching Approval when supporting records must be reviewed before final authorization.
Automation and Control Opportunities
FB60 is well suited to structured finance workflows because the required accounting information can be standardized and validated before posting. An intelligent workflow can connect invoice capture with GL coding, tax determination, approval routing, and SAP posting while preserving appropriate review controls.
Organizations can also use Purchase Order Vendor Communication practices to clarify supplier documentation, coding requirements, and purchasing references, helping finance teams receive the information needed for accurate invoice treatment.
A strong workflow should distinguish between recurring invoices, service invoices, asset-related invoices, employee-related supplier charges, and other categories because each may require different accounting assignments. Approval thresholds can likewise be aligned with business policy and delegated authority.
When invoice data is prepared for posting, the objective is not merely document entry but reliable financial recognition. Consistent validation of vendor, amount, tax, account assignment, cost object, currency, and payment terms improves the quality of downstream reporting and reconciliation.
Best Practices for FB60 Vendor Invoices
Finance teams can improve FB60 processing by establishing clear rules for when direct FI posting is appropriate and by standardizing the information required from suppliers and internal requesters.
- Validate vendor master information before posting.
- Use standardized GL-account and cost-object coding rules.
- Review tax codes and invoice dates carefully.
- Maintain clear approval thresholds for non-PO invoices.
- Reconcile posted vendor liabilities with supporting documentation.
- Monitor duplicate invoice numbers and recurring supplier charges.
These controls support accurate financial reporting while helping organizations manage supplier obligations and maintain predictable cash flow. A well-designed workflow also makes invoice status easier to trace from receipt through approval, posting, and settlement.
Summary
SAP ECC FB60 Vendor Invoice provides a direct method for recording vendor invoices in SAP Financial Accounting, particularly for non-purchase-order transactions. Its core activities include entering vendor and invoice data, assigning the appropriate financial accounts and cost objects, validating taxes and payment information, and posting the resulting accounting document.
FB60 works most effectively when supported by disciplined vendor data, clear approval policies, structured invoice capture, appropriate matching controls, and integrated payment processes. These practices help finance teams improve accounting accuracy, strengthen vendor relationships, and maintain reliable financial performance.