Maintaining the Customer PO# After Invoicing

“The customer won’t pay for this order because the PO# is missing/wrong. We need to fix it and send them a new invoice.”
Sound familiar?
We run into this issue regularly when meeting with credit teams. They hear from the customer who requires a corrected invoice. Here are some of the ways companies handle it:
  • Send the PO # in an email or over the phone, hoping that’s sufficient (it usually isn’t)
  • White out (yes it’s still a thing!), type over a printed invoice copy and scan to the customer
  • Credit and rebill – copy order to RM order, invoice it, copy to a new order, enter the correct PO, invoice it. Say it isn’t so…
If only the PO# field could be updated after the order was already invoiced. Did you know that you can maintain the PO# on orders at any stage other than canceled? And the invoice can be reprinted with the updated PO#? Wait, what?! When did they add that feature? Would you believe way back in 2011, version 6.1.001 GUI? This feature works in both GUI and CSD.
This is one of hundreds of examples of features in standard SX.e Distribution that customers are not leveraging, typical of under-utilization. Here are a few more for the AR C&C team:
  • ARIC – Credit / Credit Exposure added long ago in GUI, 11.0.0.9 CSDHint: Blank out the customer #, now access that screen
  • AR Groups – Buh-bye split payments, added 6.1.040
  • ARECR – Cash receipts REVERSAL!! added 11.19.9
  • ARECE – Payment type added 11.19.6
  • ARECE – Enter a list of invoices to pay, legacy CHUI, GUI
  • AR Lockbox – Import to cash receipts from bank, added 4.0
  • ARRCD – AR Days to Pay, added 3.2.140
  • ARRCW – AR Early Credit Warning includes ship to, 6.1.080
  • OERX – Pre-Invoice Exceptions Report, added 10.1.1

Comments