Processor Reconciliation
The Partner Portal can show processor settlement health across your linked POS customers without exposing their bank account details.
Open Partner Reconciliation.
Who this guide is for
This guide is for approved Synalux resellers reviewing settlement health for customers who explicitly have reconciliation access enabled. It is a read-only support and portfolio workflow.
You can review what has been reported and whether it has been matched. You cannot:
What the report proves
Synalux follows each settlement through:
The three verification modes are equal first-class choices:
| Customer setting | Evidence | GL destination |
|---|---|---|
| Bank feed | Cleared Plaid, Mercury, or imported bank deposit | Bank cash |
| Manual deposits | Cleared deposit recorded by the customer administrator | Bank cash |
| Processor only | Processor lifecycle reaches paid | Undeposited funds / cash in transit |
A processor batch marked closed is not reconciled. In bank modes, the customer
must fully allocate cleared deposit evidence. In processor-only mode, the batch
must reach paid and then reconcile automatically under the customer’s setting
or through an audited customer-administrator action.
The accounting sequence is:
``text
POS activity
→ Stripe or Dejavoo clearing account
→ normalized processor batch
→ bank/manual mode: cleared deposit allocation → bank cash journal
→ processor-only: paid evidence → cash-in-transit journal
`
Partial bank allocations remain open and do not create partial settlement journals.
The customer can select only a bank deposit from the same account and
currency as the processor batch. Synalux refuses a cross-customer or
cross-currency allocation even if the displayed amounts are equal.
Before you expect a customer to appear
A Synalux support administrator must:
or Detail report access;New reseller customers begin with None. Summary or Detail becomes available only after Synalux completes the customer connection. Resellers cannot create or change that connection.
Access levels
| Level | What you can see |
|---|---|
| None | Customer setup/link state only |
| Summary | Processor list, counts, reported net deposits, fees, open items, reconciled items, and exceptions |
| Detail | Summary plus individual processor batch drilldown |
Synalux support confirms the correct customer and approves the access level. Resellers cannot create or change customer connections.
Access can be reduced or revoked at any time. A revoked customer no longer contributes settlement totals. If the wrong customer appears, stop reviewing the report and contact Synalux support. These settings cannot be changed through the Partner Portal.
What the portfolio looks like
The portfolio separates customers with Detail, Summary, and None access. Only a Detail row has an expandable batch list. Summary metrics also preserve the verification mix, so a portfolio can show both the reconciled total and how many were processor-verified. The selected view includes the full approved portfolio.
Information never shown
The reseller report does not include:
Customer administrators retain the bank-matching workflow in their Accounting module.
Reported net and fee totals stay separated by currency. Synalux never adds,
for example, USD cents to EUR cents and labels the result as one currency.
Continuity transparency
When a customer whose primary processor is Dejavoo has a station switched to the
backup processor, Synalux emits a record of it so the outage is visible to you
rather than only to the venue. This is separate from settlement reconciliation:
it reports continuity behaviour, not money movement.
The dashboard groups continuity activity into six customer-facing events:
| Event | Meaning |
|---|---|
| Backup activated | an admin switches a station to the backup processor |
| Default restored | that station is switched back to the venue default |
| Backup payment succeeded | a card payment completes while the station is on the backup |
| Backup payment failed | a card payment on the backup does not complete |
| Payment needs review | a payment taken on the backup needs follow-up |
| Report generated | a partner reconciliation report is produced |
Declines and interrupted payments both contribute to the failed-payment count,
so the dashboard reflects unsuccessful attempts as well as successes.
The dashboard shows only the customer, venue, station, processors, amount,
currency, payment reference, and the operator's stated reason needed for
follow-up. Sensitive number sequences and email addresses are masked. Card data,
cardholder names, bank details, and private accounting information are never
shown.
Only customers explicitly assigned to your reseller account can appear. Ask
Synalux support to add or correct a customer; until that approval is complete,
the customer remains absent from the dashboard.
Failover itself is documented for the customer inincluding that refunds always return through whichever processor took the
original payment.
Daily reseller workflow
- processor;
- batch identifier;
- close date;
- reported net deposit;
- processing fee;
- status.
Do not describe a closed or paid processor batch as bank-reconciled. Processor status and bank proof are separate facts.
In bank modes, eligible evidence must be a cleared positive deposit with
unallocated value for the same customer and currency. Pending, ignored, and
fully allocated bank entries cannot be used.
For a processor-only customer, do not ask for a bank match. Read the
Processor-verified label and remember that the customer’s journal debit
remains in undeposited funds/cash in transit.
Reading statuses
| Status | Meaning | Reseller action |
|---|---|---|
| Awaiting deposit | Batch totals are present; no complete bank allocation exists | Watch the expected timing; escalate after normal processor/bank delay |
| Partially matched | Part of the expected deposit was allocated | Record the remaining open amount and ask the customer to review split/combined deposits |
| Reconciled | The batch completed its recorded verification mode and the settlement journal posted once | Check the verification source before describing it as bank-verified |
| Processor-verified | A processor-only customer reconciled a paid batch to cash in transit | No bank-match request; monitor processor exceptions and later cash-transfer operations |
| Exception | The batch or expected processor source needs customer or Synalux review | Escalate with the non-sensitive batch facts listed below |
A previously reconciled batch can return to Exception when the processor
later reports the payout as failed or reversed. This does not erase its original
verification label or journal. It creates an explicit accounting-review signal;
escalate it rather than describing the prior deposit or processor verification
as final.
Provider-specific expectations
Stripe
Stripe payout activity is retained as evidence. The report still depends on the payout totals and the customer’s selected verification mode.
Dejavoo
Dejavoo is mock/manual-only until production credentials and batch access are configured. A Dejavoo batch shown in a non-production demonstration uses the same accounting and reporting workflow, but it is not evidence that a production Dejavoo connection is live.
Do not describe Dejavoo as live until Synalux confirms that production activation is complete.
Common questions
Why is a paid processor batch still awaiting verification?
In bank-feed or manual mode, Paid is still only the processor’s claim and
reconciliation waits for cleared bank-side evidence. In processor-only mode,
the customer may have disabled automatic reconciliation and must use the
audited verify action.
Why does a reconciled batch say Processor-verified?
The customer explicitly chose processor-only verification. Synalux posted the
debit to undeposited funds/cash in transit, not bank cash. Historical labels do
not change if the customer later switches modes.
Why does the portfolio total differ from one bank deposit?
One deposit can fund multiple batches, and one batch can be split across multiple deposits. Fees, refunds, chargebacks, tips, and adjustments also affect the net.
Why are there multiple reported-net totals?
The reseller has activity in more than one currency. Totals remain separated
because adding unlike currencies would produce a false portfolio amount.
Why can I see totals but not a Details button?
The customer has Summary access. Batch drilldown requires Detail.
Why is a customer listed as setup pending?
Customer setup is incomplete. Contact Synalux support to verify the relationship and finish the connection.
Can I reconcile the deposit for the customer?
No. Only the customer’s accounting administrator sees eligible bank entries and saves allocations.
Troubleshooting
| Symptom | Check | Escalate when |
|---|---|---|
| Customer absent | Confirm the customer relationship is active and access is not None | Synalux support confirms access but the customer still does not appear |
| No batches | Confirm the customer has processor activity within the expected reporting window | Provider evidence exists but no report appears after that window |
| Awaiting verification too long | Check the customer’s verification mode, expected date, grace period, and payout status | The mode-specific grace period has passed |
| Partial match | Ask the customer to review split or combined deposits | Remaining amount cannot be explained |
| Processor-only exception | Check for negative net, a failed or reversed payout, payment not yet marked paid, or a missing expected daily batch | Immediately; do not ask for a bank match |
| Bank/manual exception | Record processor, batch ID, close date, and amount | Customer accounting review is required |
Escalation checklist
Before opening a support ticket, record:
Do not request or attach full bank account numbers.
Also do not send bank transaction descriptions or references, merchant-account
references, processor credentials, private settings, or screenshots containing
those values.
What support needs from you
A useful escalation says:
Northstar Cafe · Dejavoo · batch batch_123` · closed July 22 · reported net $776.00 · partially matched.
It does not include bank credentials, full account numbers, processor records, or private settings.