EPICOR Bistrack

If your business runs on Epicor BisTrack, Suppli connects to your ERP to keep your AR data in sync and automatically send payments back, so there is no double entry between the two systems.

BisTrack exports a set of files to Suppli once a day. Suppli imports them in a fixed order, so customers, jobs, and locations are always in place before the transactions that reference them.

Open orders, quotes, and AR statements are also available to your customers in the portal.

This is a daily integration, not a live one. A change you make in BisTrack appears in Suppli after the next daily export, not within minutes. That is the single most useful thing to know when something looks out of date.

When a customer pays in Suppli, the payment is sent to BisTrack automatically as third party unapplied cash, posted to the customer's home branch. Your team matches it to the correct invoices using BisTrack's Cash Matching tool, the same way you would handle any other incoming payment.

To make that quick, Suppli sends a remittance advice with every payment listing each document and amount the customer paid:

• an invoice reference and amount for each invoice

• FC for finance charges

• NSF for AR adjustments

• CN for credit notes the customer applied

• DP for deposit adjustments

So cash matching is a checklist, not guesswork. The remittance advice tells you exactly what the customer intended to pay and in what amounts.

Four payment shapes are recorded in Suppli but flagged for your team to enter in BisTrack manually rather than pushed:

1. A partly applied credit

2. A partly taken early payment discount

3. An applied deposit

4. A payment that nets to zero, for example an invoice settled entirely by a credit

Cash matching has to be done before your next file export. When Suppli sends a payment to BisTrack, it needs to be matched and posted in your unapplied cash table before BisTrack sends its next daily file. Here is why the timing matters. Until Suppli sends the payment, we hold the affected invoices so nothing overwrites them. Once the payment is sent, your daily file becomes the source of truth. If the cash hasn't posted by then, that file still shows the invoice open, and Suppli resets the balance to match it. The result is an invoice that looks unpaid in Suppli even though your customer paid it.

Refunds and voids do not sync. If you issue a refund through Suppli and the underlying invoice needs to reopen, do that in BisTrack first. The updated balance syncs back to Suppli on the next daily file.

Deposits work in both directions, but differently. Deposits that originate in BisTrack are read-only in Suppli and are applied in BisTrack. Deposits your customers pay through Suppli are created in Suppli and pushed across.

If you use Push Sync, click it once. Clicking it repeatedly in quick succession can send the same payment to BisTrack twice. If that happens, reverse one of the two in BisTrack and let support know.

Password changes on the hosted user account. This applies only if your integration runs through a remote connection to your hosted environment. If your team changes the password for the user Suppli uses, tell us immediately. Payments stop pushing until we update it on our end.

Invoices or customers are missing from Suppli.

1. Confirm the daily export job ran successfully on your end.

2. Remember that same-day changes in BisTrack will not appear until the next export.

3. If the job ran and data is still missing, contact support at support@gosuppli.com with the invoice number or customer name.

A payment made in Suppli is not showing in BisTrack.

1. Confirm the payment shows as Successful in Suppli.

2. Check your unapplied cash table in BisTrack. It may already be there waiting to be matched.

3. Check whether the payment involved a partial credit, a partial discount, an applied deposit, or a net zero total. Those are flagged for manual entry rather than pushed.

4. If it is in neither system, trigger a push retry from Suppli or contact support with the payment date and amount.

Payments stopped pushing for one specific customer. Check that the customer is enabled for trading in BisTrack and that the account is active, not lapsed, inactive, or deleted. A closed or lapsed account will reject the payment. Contact support if the account looks fine.

A payment was overwritten and the balance is now wrong. This happens when a payment isn't matched and posted in BisTrack before the next daily file runs. Contact support with the customer and invoice numbers, and we will investigate and correct the balance.

Invoice PDFs are not appearing in the customer portal.

1. Finance charges never carry a PDF from BisTrack, so a missing PDF on an FC invoice is expected.

2. If your integration pulls PDFs directly from BisTrack, this is handled automatically, and you don't need to configure anything on your end.

3. If your invoice PDFs reach us by email, confirm BisTrack is still sending them to the Suppli email address provided during onboarding.

4. Contact support with the invoice number if it is still missing.

Payments stopped pushing entirely. If your integration uses a remote connection to your hosted environment, the most common cause is a changed or expired password on that user account. Confirm the credentials haven't changed, and contact us if they have.

Email support@gosuppli.com with the customer name, invoice or payment number, and what you are seeing in each system. Screenshots of both sides speed things up.