Spring Boot receipt import project: stage, validate and report without hiding failure

What the source kit actually checks

The standalone upload controller accepts a short receipt CSV, rejects oversized or invalid bytes and ignores the caller filename for storage. A separate Boot HTTP test shows readiness tracking a test-only dependency state. These are useful pieces, but they are not one deployed import service. ReceiptApplication does not expose /contract/imports, and the local temporary file is not durable storage.

The design should create an import ID bound to an authenticated tenant, stage bytes under a generated key, persist a job state and parse records with a clear row-error contract. A worker can process bounded chunks after the request returns. The intake lesson covers the first boundary; the outbox lesson covers a database intent record for later work.

Release gates

Run the controller through the real servlet parser and proxy with configured request ceilings. Test storage failure, duplicate submissions, tenant ownership, format ambiguity, partial row errors, retry safety, retention and cleanup. Use an actual dependency indicator in readiness only when losing that dependency means the instance must stop taking new imports. Avoid putting a slow full-table query in each probe. Measure memory, disk and worker throughput with representative files before choosing the production limits.

Checked source

// Target flow; not wired into ReceiptApplication yet.
ImportId importId = intake.stage(trustedTenant, boundedUpload);
jobs.enqueue(importId);
return importId;

Verification boundary

MultipartReceiptImportTest and ReadinessHealthGroupHttpTest provide separate local intake and health checks in the downloadable Spring source kit. The excerpt is shortened; the kit contains the complete test.

Costs and limits

This is a project design, not a runnable import service. The checked upload controller and test indicator are separate from the Boot entrypoint. There is no durable store, parser, worker, tenant identity, deployed proxy or lifecycle cleanup in the source kit.

Common Mistakes

• Do not expose a test-only import route as if it were deployed.
• Do not call temporary local storage durable.
• Do not mark a job complete before row results are committed.

Read next

Spring MVC multipart receipt import: validate before storing, Spring Boot readiness health group: withdraw traffic on a required dependency failure, Spring receipt outbox command: record intent without claiming delivery, Spring Boot tenant command API project: assemble the local write path.