SAP TCodes · LessonBy Ravi M, SAP Trainer, 10 yrs · Published · SAP S/4HANA 2023 · all levels
FB60
FB60 is the SAP transaction code for Post Vendor Invoice (FI). It posts a vendor (supplier) invoice directly in FI accounts payable (without a purchase order), creating the vendor liability.
Quick answer
FB60 posts a vendor (supplier) invoice directly in FI accounts payable (without a purchase order), creating the vendor liability.
Key takeaways
- Vendor, invoice/posting date, amount.
- G/L account(s) and cost assignment for the expense.
- For PO-based invoices, use MIRO (invoice verification) instead.
- Watch out: Using the wrong variant (e.g. create vs change vs display).
Purpose
It posts a vendor (supplier) invoice directly in FI accounts payable (without a purchase order), creating the vendor liability.
Key fields and screen
- Vendor, invoice/posting date, amount.
- G/L account(s) and cost assignment for the expense.
- Tax code and amount.
- Payment terms and text.
Tips
- For PO-based invoices, use MIRO (invoice verification) instead.
- Check the vendor’s payment terms/bank data.
- Ensure the correct tax code for the expense.
Common errors
- Posting period not open.
- Wrong/missing tax code.
- Duplicate invoice (enable duplicate checks).
Common pitfalls
- Using the wrong variant (e.g. create vs change vs display).
- Missing prerequisite master data or config.
- Not checking the resulting document/postings.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Which statement is true of FB60?
Frequently asked questions
What does FB60 stand for in SAP?
FB60 is the SAP transaction code for Post Vendor Invoice (FI). It posts a vendor (supplier) invoice directly in FI accounts payable (without a purchase order), creating the vendor liability.
Which related transactions work alongside FB60?
For PO-based invoices, use MIRO (invoice verification) instead. Check the vendor’s payment terms/bank data. Ensure the correct tax code for the expense.
What is worth remembering about FB60 in practice?
Vendor, invoice/posting date, amount. G/L account(s) and cost assignment for the expense. Tax code and amount.
What tends to go wrong with FB60?
Using the wrong variant (e.g. create vs change vs display). Missing prerequisite master data or config. Not checking the resulting document/postings.