Customer invoices and credit memos posted into AR Invoice Entry

It is held open for a person, naming the invoice and the stage it stopped at. A direct AR invoice takes its number from Epicor at save time, so there is no key on the document that would let a retry detect an invoice already created. Fluent never retries an indeterminate outcome for that reason; only a conclusive rejection before the header exists is retried.

In AR Invoice Entry, as a normal AR invoice: a header, its lines, and freight or handling as miscellaneous charges, inside an AR entry group. Fluent goes through the same path the Kinetic screen goes through, so what lands is a record your team already knows how to read, not an import staged somewhere else.

Yes. Whether a document is an invoice or a credit memo is decided before anything is written, because Epicor fixes that at creation and it cannot be changed afterwards. The invoice a memo credits is set once the memo exists, and if that reference could not be set it is reported as a warning on a memo that posted correctly. Amounts are read as printed and Epicor owns the credit sign.

A missing customer, currency, payment terms, invoice date, subtotal or total; a line without a part number, a unit of measure, a quantity or a price; or a subtotal that does not reconcile with the sum of line extensions at one cent. That same list is the warnings panel on the draft, so a reviewer fixes exactly what is holding the post. Posting also waits when the agent has an approval flow, and a draft is preserved either way.

One currency per invoice, taken from the document, with only document-currency amounts written so Epicor derives the base-currency values at its own exchange rate. A line is billed in its sales unit only, never defaulted and never crossed with a purchase or inventory unit, and a unit Fluent could not match to the document's own wording blocks the post. Freight and handling are written as non-tax miscellaneous charges. Tax is not computed on this path.