(Compliance / Accounting): Show Cin7 Pay surcharges on invoices & RTF templates

Hello Cin7 Product Team,

Ticket reference: #270456.

Summary (business-critical)

Cin7 Pay applies payment surcharges, however the surcharge does not appear on the customer-facing invoice (RTF/PDF). The result is simple and damaging: the customer receives an invoice for $X, but their bank statement shows a debit of $X + surcharge. That mismatch is creating ongoing reconciliation failures for customers and their accountants, and it is driving unnecessary disputes and support load for our team.

We have been advised this is due to an architectural limitation: the surcharge is recorded outside the sale lines (e.g., in journals), and the invoice template cannot pull it through to the customer-facing document.

Why this must be addressed (factual compliance + customer impact)

1. Pricing transparency / misleading risk: Customer documentation should clearly show what was charged and why. An invoice that does not match the amount actually debited is not acceptable from a transparency perspective and creates avoidable dispute risk.
2. Tax invoice integrity: A card surcharge is treated as part of the consideration connected to the underlying supply. Where the customer is charged a surcharge, they need documentation that supports the final paid amount for reconciliation and audit purposes.
3. Commercial impact: This is already generating pushback from B2B customers because their accountants cannot reconcile bank transactions to invoices without manual workarounds. This is a direct retention risk for us and undermines trust in Cin7 Pay.

Required change (minimum requirement)

Cin7 must provide a way for Cin7 Pay surcharges to be displayed on customer-facing invoices, including RTF templates, by implementing ONE of the following:

• Option A (preferred): Store the surcharge as an Invoice Additional Charge (or equivalent) so it flows through standard invoice totals, GST handling, exports, and MailMerge fields; OR
• Option B: Add standard MailMerge fields for surcharge details recorded against the sale (payment method, rate, surcharge amount, GST treatment) so templates can print the surcharge and present the correct payable/paid total.

Acceptance criteria (clear, testable)

• When a surcharge is applied, the invoice output (RTF/PDF/email) shows:
  • a clearly labelled line item, e.g. “Card payment surcharge (Visa/Mastercard)” and the amount; and
  • totals that reconcile: the invoice total must equal the amount charged/settled (or, if your model applies the surcharge post-invoice, the document must clearly show both “Invoice amount” and “Total paid incl. surcharge” so the customer can reconcile without guesswork).
• Works for saved payment methods / auto-charged payments, partial payments, refunds/voids, and multiple payment types.
• Surcharge data is available for exports and downstream accounting integrations.

Urgency

This is not a “nice to have”. This is core accounting hygiene and customer trust. Please escalate this as a high-priority product defect/feature, and respond with:

• which option you will implement (A or B),
• the proposed approach/design, and
• the delivery plan (or an interim solution that produces reconcilable customer documentation).

Regards,