Deposits is a tab inside CentriPay → Reporting, not its own left-navigation route. The table represents returned processor funding records; it does not invent or itemize gross sales, interchange, fees, refunds, reserves, chargebacks, adjustments, or final bank-posted status. Estimated deposit date and Amount must be verified against the authorized processor and bank records.
Before you beginConfirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.
Step by step
- Go to CentriPay → Reporting with the Bar Chart 3 icon. Choose the intended configured location and date range, then open Deposits. Keep the environment and masked MID aligned with the merchant account you intend to review.
- If No deposits found appears, first distinguish a loaded empty tab from No configured CentriPay reporting locations, a loading state, a partial-location warning, or Reporting could not load. An empty returned period is not proof that no bank funding occurred.
- Read each desktop row across Type, Location, Estimated deposit date, Method, Register closures, Amount, and Detail. On mobile the same record is condensed into location, date/method, closure link, amount, and View deposit detail.
- Treat Type as the processor status/classification normalized into the deposit record. Treat Estimated deposit date as the processor-provided effective date. Neither field alone confirms when the bank posted or made funds available.
- Read Register closures carefully. No match yet means no loaded reconciliation row explicitly names this deposit ID. A Report number link opens the exact register session; more than two matches are summarized with +N in the table, while the detail lists every loaded match.
- Choose View. The dialog title uses the amount and displays Location, Estimated deposit date, Clearing method, Environment, masked MID, and Amount. The full MID and reporting credentials are intentionally not displayed.
- In Matched register closures, open the exact report/register/location link. Read whether it is open or closed and compare its displayed processor Net deposit. A link exists because reconciliation evidence names the deposit ID—not because CentriPOS independently proved bank settlement.
- Review Batch information. Related batches appear only when a closure matched to this deposit also contains source batch IDs that match batches in the currently loaded reporting result. No matched batch records does not prove that the processor never formed a batch.
- If you arrived through a URL containing depositId, Reporting opens the Deposits tab and attempts to load that exact tenant deposit directly. Changing tabs removes depositId and batchId from the URL; closing the detail removes the depositId. Preserve the identifier separately before navigating away during an investigation.
- Trace the whole chain without changing source data: processor transaction → CentriPOS receipt/payment → processor batch → deposit → north deposit reconciliation → exact register session. Confirm tenant, location, environment, masked MID, timestamps, amounts, and identifiers at every step.
- Use the processor-issued statement for fee/adjustment detail and the bank statement for final posted amount/date. Do not label a difference as a POS error solely because gross sales, batch amount, deposit amount, counted tender, and bank posting differ.
- When escalating, include the safe deposit ID, location, environment, masked MID, selected range, estimated date, amount, linked report/batch IDs, and observed bank/processor result. Never share full card data, a full MID, API keys, or reporting passwords.
- No screenshot is published for this guide because the real Amelia Grant Harbor & Hearth Reporting route returned an error instead of a loaded Deposits tab. A different screen or fabricated funding table would be misleading.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Deposits tab | Funding view inside CentriPay → Reporting; not a standalone left-navigation destination. |
| Type | Processor status or classification normalized into the deposit record. |
| Location | Configured merchant location returned with the deposit. |
| Estimated deposit date | Processor-provided effective date; not guaranteed bank-posted date. |
| Method / Clearing method | Funding or clearing descriptor returned for the record. |
| Register closures | Links created from explicit source deposit IDs in loaded reconciliation evidence. |
| No match yet | No current explicit deposit-to-closure reconciliation link; not proof of missing funding. |
| +N | More matched closures exist than the first two table chips; open detail to see all loaded matches. |
| Amount | Returned processor deposit amount; this table does not itemize gross, fees, refunds, or adjustments. |
| View / View deposit detail | Opens the funding record’s safe detail dialog. |
| Environment | Production, beta, or sandbox context of the reporting connection. |
| Masked MID | Last four digits for merchant-account verification without exposing the full identifier. |
| Matched register closures | Exact session links with lifecycle and processor net-deposit evidence. |
| Batch information | Batches connected through a matched closure’s source batch IDs and present in the current result. |
| Direct depositId link | Opens a tenant-scoped deposit detail and prepends it if it falls outside the base response. |
| No deposits found | Loaded empty result for current connection/location/range, not proof of no bank funding. |
| Processor statement | Source for processor-issued settlement, fee, and adjustment detail. |
| Bank statement | Source for final bank-posted amount and timing. |
| Rejected screenshot | Exact demo Reporting screen failed to load; no substitute or invented screenshot is used. |
Expected result
The deposit amount and funding date reconcile to its included batches, transactions, refunds, adjustments, and fees for the intended merchant account.
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
More guides
Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.