Skip to main content

A/R Customer Balance— Real-Time from the ERP

We list the systems already supported for real-time A/R Customer Balance from your ERP and how to integration new back-office ERP systems.

João Estima avatar
Written by João Estima
Updated this week

Live A/R Customer Balance, provides real-time information to logged users on your EvolutionX webstore about the customer balance. In the A/R Customer Balance module, customers can find a summary of pending balance.

New ERP Integrations for Live A/R Customer Balance

We work either directly with the API for your ERP or through a partner integrator (who provides API support) to setup Live Endpoint for new systems. This typically is a fast-tracked development to ensure you are up and running quickly. Contact our team today to discuss your options and questions.

Contents

Current ERP Systems with Live A/R Customer Balance Integrations

The following systems are already integrated for Live A/R Customer Balance and are easy to setup:

  • Acumatica

  • Prophet 21 by Epicor (P21 DCKAP Integrator, Cloras Integration)

  • Sap B1

  • ECI DDMS

  • ECI Horizon

  • Prima Software

  • Spruce

  • TIMS Software

  • Dynamics 365 using Flintech

  • Live Customer Account

Live A/R Customer Balance

The following requests and responses are examples for Live A/R Customer Balance:

Request Header

Notes:

  • Bearer Token is preferred but oAuth2 and other authorization types can be supported too (Contact DevOps to support oAuth2).

  • The Method for the endpoint should be POST.

Example Request Header:

Content-Type: application/json
Accept: application/json
Authorization: Bearer Token or username & password

Request Body

Notes:

  • The Customer Code attribute will use the references of the ERP for the account number. It is not required for the ERP to store EvolutionX IDs for these entities. If needed, the EvolutionX Customer Account can store a GUID or Record ID in the Seller Reference as well (ask DevOps if you need this value in this integration).

  • The most important field to support is:

    • customer_code — the ERP customer code as stored in the EvolutionX Customer Account Number attribute.

Example Request Body

{
    "evo_customer_id": "277504",
    "evo_user_id": "27504",
    "customer_code": "ACME001",
    "seller_reference": "01",
    "user_seller_reference": "01"
}

Response Body

Notes:

  • Not all fields are required in the response, the most critical ones are the following:

  1. customer_code

  2. balance

  • If your system doesn't have the others fields, the response can be different.

Example Request Body

{
    "customer_code": "ACME001",
    "balance": 925.51,
    "total_due": 403.92,
    "last_charge_date": "2023-02-07T16:46:15.163",
    "last_sale_date": "2023-02-08T16:37:07.657",
    "last_payment_date": "2023-02-23T15:46:44.083",
    "last_payment_amount": 3,
    "due_30_days": 120,
    "due_60_days": 283.92,
    "due_90_days": 0,
    "due_120_days": 0,
    "due_over_120_days": 0,
    "open_credits": 0,
    "credit_available": 799.6
}

ERP DIY Integration

To use this feature you need the ERP DIY Integration App see the full article.

Contact the customer success team to discuss a new Live A/R Customer Balance integration project.

Did this answer your question?