ReceiptChase Document chase desk
Request a demo

Home / Author

The person behind the product

Jimenez Julien, the operator who built the chase desk

Founder of MLJ, SASU, publication director for ReceiptChase, and the person who answers the demo requests that come through this site.

Why I built a product about asking for receipts

I did not start out in accounting. I started out building small software for small operators, and the same complaint kept arriving from a very specific corner of that world: independent bookkeepers and two person accounting shops who told me their real job had quietly become chasing paper. Not reconciling. Not advising. Chasing. One of them read me her sent folder out loud during a call in 2022, eleven near identical messages to the same restaurant owner across nine weeks, each one a little politer than she felt. That call is the reason ReceiptChase exists.

What surprised me was how universal the shape of the problem was, and how badly it was served. Practice management suites treat document collection as a checkbox inside a workflow module nobody has time to configure. Client portals put a login between a busy plumber and a photo of a gas station receipt, which guarantees the receipt never arrives. Meanwhile the bookkeeper carries the whole open list in her head, or on a legal pad, and pays for it with the first two weeks of every month. There was no tool that simply held the list, asked on a schedule, stopped asking the moment something landed, and filed the result where she already keeps her workpapers.

So I spent eleven months sitting with practices before writing the product that ships today. I watched a full charge bookkeeper in Tucson close eight sets of books in a week. I sat through a 1099 season with a firm in Missouri and counted the reminder messages: 412 in five weeks, across three staff. I learned the vocabulary that matters, engagement type, unsupported transaction, close calendar, workpaper, and I learned which shortcuts break trust. A reminder that goes out after the client already sent the file is worse than no reminder at all, because it tells the client you are not reading their email. That single rule shaped more of the product than any feature request.

I also learned what this audience will not tolerate. Bookkeepers do not want a tool that talks to their clients in a voice that is not theirs. They do not want a system that decides on its own to escalate to an owner. They do not want their client documents used to train anything. Every one of those became a hard line in how ReceiptChase behaves: your name on the message, your cadence, your naming pattern, your folders, and a policy that your client documents are yours and stay yours.

The commercial side is deliberately plain. Three prices, no per document metering, no charge for the people you are chasing, monthly billing you can stop from the billing screen. A practice with 34 clients should be able to read the pricing table once and know exactly what it will pay in March and in November. I am accountable for that being true.

Experience and expertise

I run MLJ, SASU, a French company registered with the Paris commercial court registry, from which I publish and operate a small portfolio of tools for owner operated businesses. My background is in building and shipping software for trades where the software budget is real money and the patience for a bad tool is zero. That constraint teaches you to cut everything that does not do work.

  • Eleven months of field research inside US bookkeeping practices carrying 10 to 60 clients before the first paying account.
  • Direct work with full charge bookkeepers, client accounting services leads and managing partners on close calendars, engagement templates and reviewer queues.
  • Hands on with the file plumbing that matters to this trade: QuickBooks Online and Xero transaction data, attachment handling, and folder conventions in Google Drive, Dropbox and SharePoint.
  • Responsibility for the editorial standard of everything published on this domain, including every statistic quoted on the home page.

How this product is built and maintained

ReceiptChase ships in small increments, on a schedule that respects the calendar of the people using it. Nothing that touches the chase engine or the client facing page is released between the 1st and the 12th of a month, because that is close week for most of our practices and a surprise is a cost. Larger changes go to a group of practices who agreed to look at them first, and their notes decide whether the change ships or goes back.

On the editorial side, the rule is simple: every number on this site is one we can trace. The medians in the results section come from practices that have run at least three closes on the product, measured against their own first month, and they are refreshed each quarter. Testimonials are published with the person's name, role, business and city, with their written permission, and they are removed the day a practice asks. If a claim cannot survive a client asking us to show the working, it does not go on the page.

Support is not a queue at a distance. Demo requests, questions about a stuck integration and requests to export an archive all reach a person who has watched a real close happen. When something breaks, we say what broke and when it will be fixed rather than posting a status page euphemism.

Published articles

These are the nine reports I have written for The Ledger Tape, the ReceiptChase magazine for bookkeeping practices, each one built on the same field work and checked against the source rules before publication.

Contact the author

Write to me at jimenezjulien42@gmail.com. Tell me how many client files you carry and which document is the one that always arrives last, and you will get a written reply from me rather than a form response. If you would rather talk it through, ask for a screen share and we will find a slot outside your close week.

You can also follow the work on jimenezjulien.com, on X, on LinkedIn, on Facebook and on Instagram.

Author

Page written and maintained by Jimenez Julien, publication director of ReceiptChase. Last reviewed on March 2, 2026.