A PayRequest invoice CSV is a row-per-invoice snapshot of document amounts, dates, status and tags. It is useful for handing a structured invoice list to your accountant. It is not, by itself, a bank settlement report or proof that every invoice marked Paid generated a matching receipt of money.
For a merchant preparing an accounting handoff, the useful task is to define the export's scope, verify the numbers and identify the additional records needed. Do not ask the accountant to infer these from a filename.
Know the documented invoice columns
The PayRequest Bulk Invoice Actions documentation lists ten invoice export columns: ID, Number, Customer, Amount (EUR), Tax (EUR), Total (EUR), Status, Date, Due Date, and Tags. Amount is before tax; Total includes tax. Customer can be a display name, email or client-name snapshot.
These documented columns do not include a payment transaction ID, paid-at timestamp, provider fee, refund amount or payout reference. Check the actual downloaded file rather than inventing those columns. The export's Date is the invoice date; Due Date is when payment is due. Neither should be treated as the date money reached your bank.
Define scope before exporting
Use Bulk Actions, choose Export, then Export Invoices. Exporting is a separate type from invoice actions such as Mark as Paid or Send Reminders. You can export all invoices or use selected tags; check whether the tag match is any or all.
The Export Functions documentation describes manual CSV downloads and optional tag filtering. It does not offer scheduled recurring exports. Archived items may be included unless filtered out with tags. Do not assume the export matches a status filter or date range merely because another screen was filtered.
If you need a particular accounting period, inspect the exported rows and document the date rule you apply in your working copy. Ask the accountant which date basis they need; invoice date, due date and payment date answer different questions.
Attach an original handoff sheet
Keep the original downloaded CSV unchanged and make a separate working copy. Include a short handoff note like this:
| Handoff item | Example to record |
|---|---|
| Export time | 6 October 2026, 10:00 Europe/Amsterdam; recorded by the operator |
| Entity and audience | Invoice export; tags “client-work”; any-match |
| Period rule | Working copy includes invoice dates 1–30 September; due dates not used as the period filter |
| Row control | Expected invoice IDs checked; duplicate IDs investigated |
| Payment evidence | Separate provider or bank records supplied where available; unresolved matches listed |
| Owner | Person responsible for answering scope and status questions |
This is a suggested process note, not an automatically generated PayRequest report. Record the scope you actually used, including exclusions and any uncertainty.
Check arithmetic without equating it to cash
Assume three illustrative invoice rows, each with 21% tax: before-tax amounts €100, €200 and €50; tax €21, €42 and €10.50; totals €121, €242 and €60.50. The control totals are €350 before tax, €73.50 tax and €423.50 including tax.
If the first two rows are Paid, their invoice totals sum to €363. That is a sum of document totals with that status. It does not establish the amount deposited into your bank, the collection date, deductions or later refunds. The same PayRequest documentation includes a bulk Mark as Paid action, so a status alone cannot establish which payment evidence supports it.
This arithmetic is a consistency example, not tax advice. Use each invoice's actual figures and ask the accountant how to treat tax, currencies, credits and refunds in your situation.
Inspect the spreadsheet import and repeat handoff
Keep IDs and invoice numbers as identifiers. Check whether the spreadsheet has converted a leading-zero number or a date unexpectedly. Confirm numeric amount columns, decimal separators, row count and several original rows before summing. Do not import the invoice CSV blindly into accounting software and assume its schema matches the destination.
A later export can contain changed statuses. Preserve the first snapshot and label the replacement with its export time; do not append overlapping invoice lists and double-count the same IDs.
Prepare the document list with PayRequest Invoicing. For matching the separate payment records, continue with the payment reconciliation guide. A complete handoff states what the CSV contains and what remains to verify.
Editorial note: AI assisted with this article and cover. Published documentation was checked on 6 October 2026. The handoff sheet and calculations are original examples, not a tested export, accounting certification or customer result.
