Your accountant can have a copy of your invoices without you sending them one at a time. Mucka sends one email with a spreadsheet listing every invoice and a zip with a PDF of each.
Before you start
Put your accountant's email in Settings → Business → Details, in the Your accountant card. That's the only address these go to. See Add your accountant.
Ask Mucka
Just say what you want, for example:
- "Send my accountant last quarter's invoices"
- "Email my accountant all my invoices"
- "Send the accountant October's unpaid invoices"
Mucka puts a card in your actions saying how many invoices, which dates, and who they're going to. Open it to read the email and change it if you like, then tap Send to accountant. Nothing goes before you tap.
Have them ready every month or quarter
In the Your accountant card, open Send them your invoices and tick Get my invoices ready for my accountant. Choose how often (every month, every 3 months, every 6 months or once a year) and which invoices. When each period ends, the card turns up in your actions, ready to send.
Which invoices go
You choose any of:
- Paid: money that has come in
- Unpaid: sent, overdue or part paid
- Cancelled: listed on the spreadsheet as cancelled, so there are no gaps in your numbering
Drafts never go, because your customer hasn't seen them. An invoice counts by the date printed on it, so invoices brought over from your old system land in the right month.
What your accountant gets
- A spreadsheet with each invoice's number, date, customer, status, net, VAT, total and what's been paid
- A zip with a PDF of each invoice. These are copies for the books, so they don't carry a pay online link
If there are a lot of PDFs, they come in a few emails (part 1, part 2 and so on) so they don't bounce off your accountant's inbox. The spreadsheet comes with the first one.
Why not just send each invoice?
Sending an invoice emails it to your customer as a bill, asking them to pay. Your accountant isn't paying it, and Mucka won't email an invoice that's already paid, so that would only cause confusion. Use this instead.