{{ success.zip_filename }}
(contains {{ success.csv_filename }} + {{ success.memo_filename }}{% if success.recon %} + {{ success.recon.filename }}{% endif %})
{% if internal_qa_mode and success.recon %}
PASS — every bucket ties within tolerance and no unknown PDF lines. Reserve Δ: {{ success.recon.reserve_delta }} (informational; confirm against the Date Range Report).
REVIEW — {{ success.recon.variance_count }} bucket(s) out of tolerance, {{ success.recon.unknown_count }} unknown PDF line(s) (likely Amazon layout drift). Reserve Δ: {{ success.recon.reserve_delta }}. See {{ success.recon.filename }} in the zip for details.
PARSE ERROR — the Amazon PDF could not be parsed. JE CSV is unaffected. Error: {{ success.recon.error }}
| Settlement | Rows | JE lines | Cash deposit | Reserve Δ | Unclassified |
|---|---|---|---|---|---|
| {{ s.settlement_id }} | {{ s.rows }} | {{ s.lines }} | {{ s.cash_deposit }} | {{ s.reserve_delta }} | {{ s.unclassified }} |
The dropdown lists every entity flagged amazon-enabled in your config.yaml. One file produces one journal entry per settlement id, plus a close memo flagging any rows that didn't map cleanly. Review every JE against the source document before booking — Reconcilly does not post to QuickBooks Online; you import the CSV.
{{ shopify_success.zip_filename }}
(contains {{ shopify_success.je_filename }} + {{ shopify_success.report_filename }})
Three CSV uploads, one balanced JE plus a markdown reconciliation report. The validation gate refuses to emit the JE if any FAIL check fails (JE balance, MPF cross-check, channel subtotals, chargeback bucketing) — tick Force to override and document why. WARN-severity findings (blank Source rows, unmatched adjustments, stale Manual Payment Receivable, alt gateways, reserve sign anomaly) ride on the report and never block.