See llms.txt for all machine-readable content.
This workflow monitors supplier invoice emails in Gmail, validates PDF/XML e-invoices with Dynamic Document API, stores files in Google Drive, maintains an invoice register and supplier list in Google Sheets, sends payment-due reminders by email, and exports ready invoices monthly as a DATEV Buchungsstapel CSV for your accountant.
has:attachment label:incoming-invoices arrives and downloads its attachments.ready, new_supplier, on_hold, invalid, no_einvoice, unchecked, or check_failed.alert_email when new invoices need manual review.alert_email a list of unpaid invoices due within the configured horizon (including overdue items), highlighting invoices that are still on hold.ready invoices up to the end of the previous month, emails the file to accountant_email, and updates the register rows as exported or book_by_hand.@dynamic-document-api/n8n-nodes-dynamic-document-api, 0.1.2 or later, tested with 0.1.2 on n8n 2.44.4, install guide: https://dynamicdocumentapi.com/docs/n8n). Create an API key in the Dynamic Document API dashboard and add it as a Dynamic Document API credential.label:incoming-invoices).invoices_sheet_url and suppliers_sheet_url in Inbox settings.drive_folder_id, plus update company_name, own_vat_id, alert_email, accountant_email, timezone, and (if needed) DATEV parameters like consultant/client numbers and default accounts.datev_default_creditor, datev_default_expense_account, datev_tax_keys); the defaults are SKR03, the note lists SKR04. Per supplier, the supplier list holds the creditor, expense account and a tax key for EU acquisitions and reverse chargeask_for_einvoice, and change due_within_days for the due listTested against the live API with real e-invoices: XRechnung CII, a ZUGFeRD PDF with two VAT rates, a UBL credit note, goods from an Austrian supplier (intra-EU acquisition), services from a Dutch supplier with a new IBAN (reverse charge), an XML with a wrong total, a plain PDF and the same invoice sent twice. Each ended in the expected status, draft or skip; a second run of the same emails added nothing. The DATEV file passed the field patterns of DATEV's format check program, and a second export found nothing to book. Replies are always drafts. The JSON contains no credentials or private IDs. Agree the DATEV accounts and tax keys with your accountant before the first import.