Home/Notes/What an accountant needs to know about CSV exports
What an accountant needs to know about CSV exports
4 Mar 2026
How an accountant deals with CSV exports — and what usually goes wrong.
The problem: a www record that disagrees with the apex. The CSV exports data is out of sync for an accountant.
We check CSV exports for an accountant once a quarter. It takes five minutes and has caught two problems in the past year. Both would have caused downtime within a week.
The job started when an accountant realised their CSV exports had been wrong for months. Nobody noticed because the site still loaded.
Search consoles like honest sitemaps. Every loc should be a document. Reserving ten thousand empty shells and hoping Google does not notice is not a strategy for CSV exports.
Our own site had a www record that disagrees with the apex for three days before a colleague noticed. We added it to the pre-launch checklist the same afternoon.
Two-factor on the registrar account is the single highest-value thing we do for an accountant when managing CSV exports. Everything else can be rebuilt; a stolen domain cannot.
Related work on this site follows the same principle: one job, a real inbox, no theatre. an accountant did not need four analytics dashboards to know that Tuesdays are slow.
Every CMS update brings a small chance that CSV exports breaks. For an accountant, we pin versions and test upgrades in a staging copy before touching production.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com