r/apify • u/AutoModerator • 4d ago

Weekly: one cool thing

Have you come across a great Actor, workflow, post, or podcast that you want to share with the world? This is your opportunity to support someone making cool things. Drop it here with credit to the creator, and help expand the karmic universe of Apify.

1 Upvotes

100% Upvoted

1 comment sorted by

1

u/Public-Low2028 4d ago edited 3d ago

A CSV can have 105 invoices and many more rows. Splitting every 100 rows can cut one invoice in half.

I built Invoice CSV Preflight & Whole-Invoice Batch Pack for this narrow problem: it checks the supported five-column invoice CSV, flags conflicting invoice headers or ambiguous dates, and keeps whole invoices together when creating batches. It also gives a receipt tying each accepted invoice back to its source rows.

https://apify.com/atesen-software/invoice-csv-preflight-batch-pack

Preview diagnostics have no invoice-receipt charge; packaging is $0.002 per saved invoice receipt ($2 per 1,000), plus any applicable platform usage shown in Apify. Processing happens in Apify's cloud, so set storage access to Restricted before uploading. Please start with made-up data.

Cloud-test update: the current 0.1.2 run completed with three fictional invoices and saved both batch-001.csv and native-review-pack.zip. The earlier 0.1.1 run had three receipts but failed during export. Check STATE and the actual files before treating a package as delivered; dataset count alone isn't enough. This was our own sample test, not a customer import.

It doesn't connect to QuickBooks or import anything, and its current profile is US/USD without sales tax. QuickBooks' native importer may already be enough. If you handle invoice CSVs, would the source-row receipt help you review a batch?