CentriPay → Reporting uses the Bar Chart 3 icon. The screen requests at most 500 cloud reporting records and separately loads up to 500 local NMI gateway records. Its numbers are operational reporting evidence, not a bank statement: processor time, sale time, register-session scope, batch close, estimated deposit date, and bank posting can all differ.
Step by step
- Go to CentriPay → Reporting using the Bar Chart 3 icon. Only locations with a saved and tested Payanywhere reporting connection are included. If No configured CentriPay reporting locations appears, finish and test the location connection before interpreting the empty page.
- Choose All configured locations or one location, then apply a preset or custom date range. Choose Refresh to rerun the reporting request. Refresh is not a bank-posting confirmation and does not change a register closure or accounting record.
- Read the four headline tiles independently. Cloud gross is cloud processor volume/count; Deposited is the synced deposit amount/count; Batches is the returned batch amount/count; Gateway is approved local NMI volume while its count includes every local gateway record in range. Do not add these tiles together because they overlap different stages and sources.
- Use Latest deposit and Top location as orientation only. Location performance ranks by net payment volume and visibly renders the first six configured locations, showing environment, masked MID, transaction count, and approval rate. A location below the first six is still in the selected reporting result.
- Review Payment health. Approved and Declined come from the processor summary. Refunds counts cloud transaction types containing refund. Confirm the underlying rows before using these counts for reconciliation or coaching.
- Read Settlement path as a guide—Payments → Receipts → Batches → Deposits—not proof that every step is linked. Receipts says Linked when POS sale exists. Open batches treats open, pending, or not-closed/non-settled records as open and visibly lists only the first four.
- If Some configured locations could not be queried appears, record every named location, environment, masked MID, and message. The remaining tiles and tables are partial; do not reconcile an all-location period until the failed locations are resolved or explicitly excluded.
- Open Transactions. Source cards distinguish Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, and unclassified Payments Hub activity. The cloud table shows Date, Location, Source, Type, Card, Amount, Status, Auth, and Receipt / TXN; choose the receipt link only when a POS sale ID exists.
- Below the cloud table, NMI Gateway Local Activity shows local POS-stored gateway records in the date range and renders only the first ten. Its approved amounts feed the Gateway volume tile, while declined or other statuses remain in the record count. This local list is separate from the cloud transaction result.
- Open Deposits to review Type, Location, Estimated deposit date, Method, Register closures, Amount, and View. No match yet means the displayed deposit ID has no link in the loaded register-closure reconciliation evidence; it does not prove that funding or the register activity is absent.
- Choose View on a deposit. Confirm the location, estimated deposit date, clearing method, environment, masked MID, and amount. Matched register closures show their report/register/location, lifecycle, and processor net deposit. Batch information appears only when the matched closure evidence also contains related source batch IDs.
- Open Batches to review batch date, location, status, closed time, matched register closures, amount, and detail. The detail repeats environment and masked MID and links only those closures whose reconciliation evidence names the batch ID. A closed or settled batch is not by itself proof that its deposit posted to the bank.
- Open Statements. These rows are generated in CentriPOS by grouping the currently loaded deposits by effective-date month and batches by closed/opened month. They show period, unique represented locations, deposit count, batch count, and net deposited; they are not processor-issued statement documents and do not show fees.
- Choose Register closures to compare the selected reporting evidence with the exact session report. Closure matching reads recent reconciliation rows and associates only explicit source deposit IDs and source batch IDs. Trace a representative payment → POS receipt → batch → deposit → closure and keep location, environment, MID, date/time, amount, and identifiers aligned.
- For final cash settlement, fees, adjustments, chargebacks, or bank-posted timing, use the authorized processor and bank statements alongside CentriPOS. Capture the active filters and identifiers before escalating; never paste full card numbers, credentials, or an unmasked merchant ID into support notes.
- No screenshot is shown for this guide because the real Amelia Grant Harbor & Hearth /centripay/reporting capture ended in Reporting could not load: Unknown error. That rejected state is not replaced with another route, mockup, or invented image.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Bar Chart 3 icon | Exact CentriPOS navigation icon for CentriPay → Reporting. |
| Configured location | Location with a saved and tested Payanywhere reporting connection. |
| Location filter | All configured locations or one returned configured location. |
| Date range | Preset/custom processor query window; local gateway rows are filtered against the same from/to timestamps. |
| Refresh | Reruns the reporting request; does not confirm bank posting or mutate closures. |
| 500-record boundary | The screen requests up to 500 cloud reporting records and loads up to 500 local gateway records. |
| Cloud gross | Processor gross volume and processor transaction count for the returned scope. |
| Deposited | Synced deposit total and count; not an independent bank-statement total. |
| Batches | Returned batch amount and count. |
| Gateway | Approved local NMI amount; displayed count includes all local gateway statuses in range. |
| Latest deposit | Most recent returned deposit by effective date. |
| Top location | Highest net-volume configured location in the returned result. |
| Location performance | Ranks all returned configured locations but visibly renders the first six. |
| Payment health | Processor Approved/Declined counts plus cloud transaction types containing refund. |
| Settlement path | Orientation from Payments to Receipts to Batches to Deposits; not proof that each record is linked. |
| Open batches | Open/pending or otherwise unclosed/unsettled batches; first four are shown in the card. |
| Partial-query warning | Named configured locations failed; combined totals are incomplete. |
| Source cards | Cloud / terminal, Tap to Pay on iPhone, NMI Gateway, and unclassified Payments Hub counts/volume. |
| Transactions table | Cloud reporting rows with time, location, source, type, card summary, amount, status, auth, and receipt/processor reference. |
| Receipt link | Available only when a processor row carries a CentriPOS sale ID. |
| NMI Gateway Local Activity | Separate local POS-stored list; first ten rows rendered. |
| Deposits tab | Funding records with estimated date, method, amount, and reconciliation-derived links. |
| Batches tab | Settlement groups with status, open/close timing, amount, and reconciliation-derived links. |
| Statements tab | CentriPOS-generated monthly grouping of loaded deposits and batches—not a processor-issued statement. |
| No match yet | No explicit reconciliation link for that displayed deposit/batch ID in the loaded evidence. |
| Register closures | Opens closure reporting for session-level comparison. |
| Rejected screenshot | The exact Harbor & Hearth route ended in an error, so no screenshot or substitute image is published. |
Expected result
The processor totals, fees, batches, deposits, refunds, and disputes reconcile with the selected merchant, date, and settlement scope.
Troubleshooting
- Check the processor transaction status before retrying an uncertain payment or refund.
- Confirm the terminal, register, amount, and transaction reference all belong together.
- Never include full card numbers or protected credentials in a support request.
CentriPOS API explorer · API Center administration