Fiest Developers

Accounting reports

Read sales, VAT and refund totals, and check payment allocations before importing them.

Use the accounting summary for sales, VAT, refunds, tips and gift-card totals. Use the payment report to check how those amounts are allocated between payment methods.

Read both reports for the same restaurant and business dates. Amounts are integer cents. The reports describe accounting activity; they do not confirm bank settlement or provider fees.

Read and reconcile

  1. Use an authorized restaurant connection. Partner API reads need fiest.restaurant.read and fiest.accounting.read. MCP report reads need fiest.restaurant.read and fiest.analytics.read.
  2. Choose the same dates, currency, timezone and business-day cutoff for both reports. Each period may contain at most 31 business dates.
  3. Check the reconciliation and warnings. Use adjusted payment allocations only when the payment report has status: ready and they match the accounting summary. If the reports disagree, read both again.
  4. Use adjusted payment rows instead of raw rows when importing a ready allocation. Never add both sets together. Keep tips and gift-card liabilities separate from taxable sales.

Do not convert missing amounts to zero or import a report with unresolved VAT or payment evidence. Match payment methods to your bookkeeper's accounts.

Report status

StatusWhat to do
readyReconcile the adjusted payment amounts with the accounting summary before import.
review_requiredReview the warnings before importing adjusted amounts.
blocked_staleRead the reports again and resolve the changed source data.

If adjustedRows is null, no usable adjusted allocation is available. Do not substitute raw values as though they were corrected values.

Refund dates and signed amounts

A refund reduces sales on its refund business date. The original sale stays on its sale date. For example, a EUR 20 sale on Monday and a full refund on Friday produce EUR 20 on Monday and EUR -20 on Friday.

Sales, VAT and payment allocations may therefore be negative. Refund amounts and counts are positive. Keep the signed values returned by the API, and do not subtract refundsMinor from sales again. Sales totals already include applicable refunds.

When present, refundBreakdown separates the refund total into:

FieldWhat was returned
salesMinorProduct sales, including VAT.
tipsMinorTips.
deferredGiftCardsMinorGift-card purchase liability.
nonSalePaymentsMinorPayments that did not become completed sales.
unallocatedMinorReturns that need further review.

These amounts sum to totals.refundsMinor. Some refunds are outside sales, so the full refund total is not a product-sales deduction.

Check refundBreakdown.evidenceStatus and the report warnings. An absent breakdown means unavailable, not zero. If refundReporting.legacyTiming or refundReporting.incompleteEvidence is true, review the affected period before importing. Older records may lack individual partial-refund dates.

See Refunds to import individual refund events.

Re-imports and reversals

Save the reports, period and calculation versions with each import. Compare a new report with the saved one before posting changes, so reading the same period again does not create duplicate entries.

If payment allocations change, import only the difference. A reversed allocation reverses the previous change; it does not create another sale or change total VAT. If sales or refunds have changed too, reconcile the whole period again.

On this page