Self-billed e-invoices: reporting what your supplier will not

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can say which of GadgetSphere’s purchases you have to report yourself, set a supplier up so the e-invoice is built and sent without anyone touching it, read the five blanks that divert one and the two that let it go out wrong, name what runs for you and what will wait for you forever, and avoid the three traps that have cost other people valid e-invoices.

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

Presentations

1. When the obligation is yours, not your supplier’s — about 10 minutes, narrated
2. Which documents can carry one, and how the flag gets set — about 11 minutes, narrated
3. Set the supplier up so it works — about 12 minutes, narrated
4. The blanks that divert it, and the blanks that let it go out wrong — about 12 minutes, narrated
5. What runs for you, and what never will — about 13 minutes, narrated
6. The traps, and proving the month — about 12 minutes, narrated

Modules this series draws on

• E-Invoice & PEPPOL Module
• Purchasing 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
• Purchase Invoice (Internal)
• Employee Maintenance
• Organization
• Supplier
• Purchase Debit Note (Internal)
• Purchase Refund Note Applet (Internal)
• Cancelling and Correcting a Validated E-Invoice
• Incoming Supplier E-Invoices
• The Month-End E-Invoice Cycle (1st to 7th)
• E-Invoice Pools & Submission Routing
• E-Invoice Validation Rules & Troubleshooting
• Peppol Configuration Guide
• Use Cases
• Purchasing Module
• Related Applets

All presentations · Presentations for the whole-system operator