Handle the e-invoice requests your buyers raise
For the whole-system operator — you run the books. Level 2 — operate.
By the end you can run the seller’s side of buyer-raised e-invoice requests at GadgetSphere: tell the two request paths apart and say which finishes itself, find the requests nobody told you about, trace what one request does to a document and to your month, read the buyer’s own status screen the way they read it, diagnose the six complaints that actually arrive, and set the path up so buyers can use it before the month closes.
Before this series: Run the month-end e-invoice cycle
Presentations
- Two doors, and only one rings a bell — about 9 minutes, narrated
- What one buyer’s request does to your month — about 11 minutes, narrated
- Read the buyer’s screen before you answer — about 10 minutes, narrated
- The complaints you will actually get — about 11 minutes, narrated
- Open the door properly, and know when it closes — about 11 minutes, narrated
Modules this series draws on
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
- MY E-Invoice Portal Applet
- Storefront E-Invoice Request
- The Month-End E-Invoice Cycle (1st to 7th)
- E-Invoice Pools & Submission Routing
- Consolidated e-invoices
- Pools and queues
All presentations · Presentations for the whole-system operator