Fraud Blocker

Clarity Connect integration

Authorize.net Sage 100 Integration

Post settled Authorize.net transactions to Sage 100 Accounts Receivable as cash receipts, batch by batch, so AR matches what the gateway settled.

Authorize.net and Sage 100 kept in sync through Clarity Connect

What moves between Authorize.net and Sage 100

Authorize.net authorizes and settles the card and eCheck payments; Sage 100 records them against customers and invoices. Clarity Connect reads the gateway's transaction records and writes the matching receipts, refunds and deposits into Sage 100.

Gateway

Authorize.net

Where payments are authorized and settled

  • Transactions
  • Settled batches
  • Refunds and voids
  • Webhook events
Clarity Connectper event or per batch
ERP

Sage 100

Where receivables are recorded

  • AR customers and invoices
  • Cash receipts
  • Deposits
  • Credit memos

Authorize.net to Sage 100 record mapping

A first map. Discovery confirms how invoice numbers travel with each payment and which accounts post where.

Authorize.netSage 100Direction
Settled transactionCash receipt applied to an invoiceAuthorize.net to Sage 100
Settled batchCash receipts depositAuthorize.net to Sage 100
RefundCredit memoAuthorize.net to Sage 100
VoidNo receipt posted (a voided transaction doesn't settle)Authorize.net to Sage 100
Invoice number on the transactionAR invoiceSage 100 to Authorize.net

How the payment sync works

One settled batch, one Sage 100 deposit

Authorize.net groups transactions into a batch every 24 hours and submits it for settlement, one payment type per batch. Connect reads the settled batch list and each batch's transactions through the Transaction Reporting API, then writes the cash receipts and a deposit that matches the batch.

Events as they happen

Authorize.net webhooks announce events such as net.authorize.payment.authcapture.created, refund.created and void.created. Connect can use them to flag the Sage 100 order as paid straight away, and let the run after each settled batch confirm the money.

Card data stays with Authorize.net

With Accept.js or Accept Hosted, card details go straight to Authorize.net and your server receives a payment nonce in their place. Sage 100 receives the transaction ID, amount, date and invoice reference, never the card number.

See Clarity Connect move an order

Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.

Book a demo

Alongside Sage 100's own card processing

Sage 100's built-in Credit Card Processing works through Paya (formerly Sage Payment Solutions). Companies that already take payments on Authorize.net, for a web store or a customer portal, still need those payments in Sage 100 AR, and that is the gap this integration fills.

For invoice payments, card-on-file and ACH on Authorize.net with receipts posted to Sage 100, see Sage 100 payment processing and Clarity's Authorize.net gateway page. Stored cards use Authorize.net's own customer profiles (CIM), so the tokens stay with Authorize.net.

How Clarity Connect runs it

Clarity Connect is Clarity's integration platform. It keeps Authorize.net and Sage 100 linked and runs each job, event updates during the day and settlement posting after each batch, as a separate task. If Sage 100 is unavailable, jobs wait in a retry queue rather than being lost. Clarity has built more than 3,000 integrations on Connect; recorded demos are in our video playlist.

How a Clarity Connect project runs
  1. Discovery

    A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.

  2. Tasks and mapping

    Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.

  3. Testing

    Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.

  4. Live, with a dashboard

    Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.

Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.

Questions

Does Sage 100 or Clarity Connect see card numbers?

No. Authorize.net handles the card data; the integration moves transaction IDs, amounts, dates and invoice references into Sage 100.

When do payments appear in Sage 100?

A webhook can flag a payment as soon as it is captured. The cash receipts and deposit are usually posted once Authorize.net settles the day's batch, so Sage 100 matches the bank.

Can we keep Paya for some payments?

Usually, yes. Sage 100's own Credit Card Processing can keep handling the payments it takes today, with Authorize.net receipts posted alongside.

How is Clarity Connect priced?

SaaS at $599 a month, or a one-off $15,000 license without annual fees; projects beyond that are priced to scope. See pricing.

Related resources

Connect Authorize.net and Sage 100

Tell us where you take payments on Authorize.net and how your AR team posts them in Sage 100. A Clarity business analyst will map receipts, deposits and references with you before anything is built.

Book a demo