The company's finance group had reached a breaking point with SyteLine. The implementation left the team underequipped, undertrained, and increasingly convinced the software itself was the problem.
On the surface, customers appeared as if they were set up correctly. Credit limits were set to zero and terms showed as PIA.
But credit hold wasn't being controlled at the order level, only at the customer. So, instead of removing credit hold order-by-order, they were effectively taking all orders off credit hold for a single customer and hoping the shipment transactions were processed correctly. Then, putting the customer back on credit hold.
While the orders were entered into the ERP, the business was manually creating "invoices" outside of SyteLine so the customer had a document to pay against. When the payment arrived they would record it as an "open credit" and wait for the system-generated invoice to be available for application.
However, they only request prepayment as items are ready to ship. Tracking what had been requested, versus paid, versus applied, was becoming complicated.
This process required them to touch each cash receipt at least twice. Sometimes more if the payment was applied incorrectly.
Credit card orders are processed via a third-party web application. Payment is captured by the ecommerce application. But the payment is based on it's calculation, not SyteLine's. This created two issues to solve:
1) Update the integration to force SyteLine to use the web application's amount and resolve any future payment discrepancies.
2) Train the finance team how to resolve payment discrepancies during the payment application process.
We started with a conversation.
The finance group had been directed by their implementation team to use open credits when recording cash received in advance of a system-generated invoice.
While that is a viable answer, it wasn't their answer.
They didn't just need to record cash. They needed a way to create a system-generated invoice that customers could pay against before their product would be shipped.
They also needed a way to account for the rounding variances introduced by credit card prepayments.
These distinctions matter.
Those small amounts were left to carry forward, quietly piling up as unresolved balances on the aging report. Existing residual balances were handled through the residual balance utility, while new payments utilized the allowance field to balance SyteLine until the larger rounding issue was resolved at the integration level.
Those open credits? They piled up too. Because multiple prepayments were in process for the same customer and/or customer order at any given time.
The Solution: Progressive Billings.
It generates an invoice by line item before shipment; even if the order is on credit hold. This solved the invoicing issue, the application issue, and even the tracking issue of what's been invoiced vs. shipped.