Automated Bukku Peppol Delivery Status Check
Every morning, WebRun opens Bukku, reads the Peppol network delivery status of every e-invoice sent to a business customer, checks Xero for the customers who share which invoices have posted on their end, and posts your team a Slack list of any transmission that is stuck, failed, or unconfirmed.
How do I confirm my Peppol e-invoices were actually received?
WebRun checks the Peppol network delivery status of every e-invoice sent from Bukku each morning, and for customers who also keep books in Xero, confirms the bill actually posted on their end. It then posts your team a Slack list of anything failed, stuck, or unconfirmed, so a silently dropped e-invoice never goes unnoticed.
- Failed or stuck Peppol transmissions surface the same morning
- Delivery is cross-confirmed against Xero for shared customers
- No e-invoice silently disappears between networks
Built for Malaysian SMEs · B2B exporters · finance managers · accounting firms
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.bukku.myin a real browser with your saved login - no setup, no API keys. -
1
Bukku - check Peppol network delivery status
bukku.my
WebRun opens Bukku to check Peppol network delivery status. - Open Bukku and list e-invoices sent through the Peppol network in the last 24 hours
- Read the network delivery status on each: delivered, failed, or awaiting acknowledgment
- Note the receiving business's Peppol ID for each invoice
Done when Every Peppol e-invoice sent since yesterday has a confirmed network status.
-
2
Xero - confirm receipt with shared customers
xero.com
WebRun opens Xero to confirm receipt with shared customers. - For customers known to run their accounts payable in Xero, check whether the matching bill has been recorded on their side
- Note any Bukku-confirmed delivery with no matching Xero bill yet
- Skip customers not on Xero. Their status comes from Bukku's network confirmation alone
Done when Every checkable customer's receipt is cross-confirmed against Xero.
-
3
Slack - flag anything stuck or failed
slack.com
WebRun opens Slack to flag anything stuck or failed. - Post a list of e-invoices that failed transmission, are still awaiting acknowledgment, or show delivered in Bukku with no matching Xero bill
- Flag anything stuck for more than a day
- Leave any resend or follow-up call to your team
Done when Your team has today's Peppol exceptions in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it resend failed e-invoices automatically?
No. Resubmitting an e-invoice is a filing action, so WebRun only flags what failed or is stuck. Resending it through Bukku is always a decision your team makes.
Why does it check Xero as well as Bukku?
Some of your business customers keep their own books in Xero. Checking there confirms the invoice was actually recorded on their end, not just accepted by the Peppol network.
What happens to customers who do not use Xero?
Their status comes entirely from Bukku's own Peppol network confirmation. Nothing about them is skipped, just the extra Xero cross-check.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.