Skip to content

Post purchase invoices and track the booking status

Updated:

Post approved invoices in bulk and see per month what is still open before closing.

Open Invoices in Fiatto
In this article

You post approved purchase invoices to your accounting package or the Fiatto ledger. On Accounting → Purchase invoices (/dashboard/invoices) you work through the posting worklist; the tab Booking status per month (/dashboard/invoices/boekstatus) shows what still needs doing per month before the month-end close.

Steps

  1. On Purchase invoices, pick a worklist under Booking status: Ready to post, Posting failed or ⚠ Posting outcome uncertain; each filter shows the number of invoices.
  2. Tick invoices and click Post selected (up to 25 at a time). Each invoice goes through the same checks as on the invoice detail; afterwards you see how many were posted, scheduled, skipped or failed, with the reason per invoice.
  3. Open the tab Booking status per month. Per month you see To book, Approved, not booked, Not staged and Failed, and whether the month is Ready for closing. Click a number for the invoices behind it, with their state and an explanation.
  4. Resolve open items on the invoice detail (stage again, fix a posting error) and export the list with Export CSV if needed.

Tips

  • With ⚠ Posting outcome uncertain the invoice may already be in the package: check that before trying again.
  • A posting that runs too long counts as stuck and may then be released again; for SAP this takes longer because its queue retries by itself.
  • Purchase credit notes only go through the connection to packages that support them — see create a credit note.
  • Booking status per month is also open to accountants and auditors.
  • The connection itself is set up via accounting connection.
  • An invoice with several VAT rates (for example 9% and 21%) is booked with its own booking line and VAT code per rate, provided the split per rate adds up to the invoice's VAT.
  • For each booking line, the booking panel shows under Why this account which source chose the ledger account (for example the category of the order line, a fixed coding rule, earlier invoices from the supplier or the booking agent) and where the cost centre and project come from. Without an order line, the cost centre and project are inherited from the linked contract, or from the asset or vehicle behind it. If you change two invoices from the same supplier to the same account, the panel offers Make this a coding rule. An invoice from a staffing agency without a valid Wtta licence gets the same check on approval as the order: see managing suppliers.
  • Group by on Purchase invoices groups the list by supplier or by Due month, showing per group the count and subtotal excl. VAT of the invoices on that page. An invoice that is booked, (partly) paid or included in a payment batch can no longer be deleted.

AP cockpit

The AP cockpit tab (/dashboard/invoices/cockpit, for approvers) shows over the last 12 months how smoothly invoices flow through the process: Touchless rate (approved without human touch), the number of invoices, Exceptions and Cycle time → posted, followed by the touchless rate per month, the Match status and the Top exception reasons. Exceptions per supplier lists the ten suppliers with the most exceptions in the last three months; Set policy gives such a supplier its own matching policy. If the small expenses route is on, its key figures appear here too.

Under Less manual work: one step per supplier you see the five suppliers with the most manual work in the last three months, each with one step: Create a coding rule, Link a contract or Request an e-invoice. An automatic invoice whose coding someone changed by hand also counts as manual work. Request an e-invoice emails the supplier on behalf of your company and in the supplier's language, explaining Peppol; the step then shows when the request was sent, and it does not come back for 30 days.

Was this article helpful?
View all articles in this topic

Find another answer

A task, feature or short question is enough.