AltirasPay

Turn Accounts Receivable Into a Payment Network.

Your customer should not have to call accounting every time they want to pay an invoice.

Build a customer payment environment around the relationship.

How the money moves

ORDER TO RECONCILIATION
  1. 01
    Customer Account
  2. 02
    PO
  3. 03
    Order
  4. 04
    Invoice
  5. 05
    Card / ACH
  6. 06
    Payment
  7. 07
    ERP
  8. 08
    Reconciliation
WHAT WOULD YOU LIKE TO FIX?
Customers call to pay every invoice
Give them a portal
Commercial cards cost more than they should
Send the enhanced data
Large customers should not be on cards
Offer ACH
Nobody knows what is actually paid
Automate the statuses

What we actually do about it

Customer Payment Portal

Allow approved customers to handle their own account without a phone call.

  • See invoices
  • Pay invoices
  • Save payment methods
  • Review payment history
  • Download receipts

Commercial Card Optimization

Transmit enhanced eligible B2B transaction information where supported. Nearly every card touching a distribution account is a commercial card, and most merchants who qualify are not sending the fields.

ACH

Give larger customers an economical electronic payment option, which by value will usually be most of the volume.

Card-on-File

Create properly authorized repeat-payment workflows for established business customers. A stored-credential transaction disputed without written authorization is hard to defend.

ERP Connectivity

Connect payments to the records that already exist.

  • Customer
  • PO
  • Invoice
  • Order
  • Settlement

Receivables Automation

Every invoice should have a status anyone can read.

INVOICEDDUEPAYMENT INITIATEDPAIDPARTIALLY PAIDPAST DUERECONCILED

Your payment architecture

AltirasPay is not the acquiring bank, the processor, the gateway or the payout institution. We help work out what needs to happen, what technology is needed, which rails fit, what the bank needs to see and which partners may fit. Final underwriting, pricing, approval, supported transaction types and rail availability remain with the acquiring bank and payment provider.

  1. CUSTOMER
  2. PURCHASE ORDER
  3. INVOICE
  4. PAYMENT PORTAL
  5. CARD / ACH
  6. ERP
RUNNING ALONGSIDE
LEVEL 2 / 3 DATA
CARD ON FILE
CONTRACT PRICING
PAYMENT HISTORY
STATUS TRACKING
SETTLEMENT

Build My Accounts Receivable Payment Flow.

Send a sample invoice and a month of card volume, and we will map the portal and the cost side together.

OTHER VERTICALS