Read a rejection and fix it

For the whole-system operator — you run the books. Level 2 — operate.

By the end you can find every rejected and every held document at GadgetSphere, read the error text well enough to name whose check failed and which record it points at, correct the master data at the source so the next sale is right too, resubmit and watch it to Valid, say which parts of the recovery run without you and which never will, and recognise the handful of documents that will not go at all no matter what you press.

Before this series: Run the month-end e-invoice cycle

Presentations

1. Find every rejection you have — about 11 minutes, narrated
2. Read the error and tell whose it is — about 10 minutes, narrated
3. The error families and the record behind each — about 12 minutes, narrated
4. Fix it at the source, not on the e-invoice — about 12 minutes, narrated
5. Resubmit, and prove it landed — about 11 minutes, narrated
6. What runs without you, and what never will — about 11 minutes, narrated
7. When a document will not go at all — about 11 minutes, narrated

Modules this series draws on

• E-Invoice & PEPPOL Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• My E-Invoice Admin Applet
• Storefront E-Invoice Request
• Customer Maintenance
• Organization
• The Month-End E-Invoice Cycle (1st to 7th)
• E-Invoice Pools & Submission Routing
• E-Invoice Validation Rules & Troubleshooting
• Consolidated e-invoices
• Pools and queues
• Validation and clearance
• E-Invoice Submission Mechanics

All presentations · Presentations for the whole-system operator