Registration Forms and Payment Reconciliation: Closing the Gap With Finance

Registration forms collect two things at once: who is attending, and how much they paid. Finance sees the second half as lump-sum deposits in a bank account, and has to match those deposits to registrants by hand. The gap grows with every discount code, partial refund, and group booking. A form that carries the right identifiers into both Salesforce and the payment processor closes it.

Why Deposits Do Not Match Registrations

A processor such as Stripe groups many payments into one payout. Stripe’s payout reconciliation report exists to match each payout that reaches the bank with the batch of payments and other transactions behind it, and it lets teams attach custom metadata to speed up that matching. The deposit equals the sum of charges, minus fees and refunds. Without a link from each charge back to a registrant, finance cannot say which registrations a deposit covers.

Identifiers That Make Matching Possible

Three identifiers do the work:

• The processor’s payment ID ties a charge to the payout.
• The registrant’s Salesforce record ID ties the registrant to the CRM.
• A shared reference, such as the registration number, appears in both systems.

When the form stores the payment ID on the registration record, finance can search the CRM for the payment ID from the payout report and find the registrant in one step.

What Finance Needs on the Record

A registration record that supports reconciliation holds the amount charged, the discount applied, the payment ID, the payment status, and the registrant’s contact. Refunds update the same record instead of living in an email thread. Group registrations need one payment tied to several attendees, which a repeatable section in the form can represent.

Where FormAssembly Fits

FormAssembly’s payment integrations work with Stripe, PayPal, Chargent, CyberSource, iATS, FreshBooks, and Authorize.net through the Payment Connector add-on. The Stripe connector creates form fields for the Stripe customer, setup intent, and payment intent IDs, and FormAssembly’s help center notes that Stripe IDs can travel to Salesforce with the rest of the submission. Formulas calculate totals and discounts before the charge. Forms connect directly to Salesforce, so the registration, the amount, and the payment ID land on the same record.

Business operations teams in higher education, nonprofit, and financial services organizations that run conferences, courses, and events can hand finance a payout report and a Salesforce report that match line by line.