If Teampay stops working, the spending does not stop, so the first priority is a temporary way to capture every expense and receipt until the tool returns. Then work on the fault: confirm whether it affects everyone or one person, note the exact message, and contact the vendor's support with specifics. we cannot describe the product's features or terms, so use its help pages for product details.
Is it one person or the whole team?
| Pattern | Probable cause | Action |
|---|---|---|
| One person fails, others fine | Account, device or permission | Ask an admin to check access; try another device |
| Everyone fails | Service or company setup | Check any status notice; contact support |
| Only receipt upload fails | File size, type or connection | Reduce file size; try again on another network |
| Only approvals stuck | Workflow setup or absent approver | Check who is assigned; ask finance |
What is the fallback log?
Share a single sheet that every team member can add to, with these columns: date, person, vendor, amount, purpose, payment method, receipt saved (yes or no) and where. Ask people to photograph each receipt straight away and store it in a shared folder named by month. That is enough to reconstruct everything later.
Worked example: a four-day outage
Say four people spend during the outage and log these: travel ₹1,850, client lunch ₹2,460, courier ₹380, software add-on ₹3,200, parking ₹240 and printing ₹690. The total is 1,850 + 2,460 + 380 + 3,200 + 240 + 690 = ₹8,820. When the tool returns, finance enters six lines and attaches six receipts, and a quick count shows six entries against six receipts. If five receipts were saved for six lines, the sixth person is asked before month-end, not three months later.
What should you do when the tool returns?
- Enter outage-period expenses in date order and tick them off the sheet.
- Check the total of the sheet against the total entered.
- Confirm card or bank statements show the same amounts.
- Ask the vendor whether anything entered just before the outage was saved.
- Keep the sheet for the month, then archive it.
Where does SpendixAI fit, and where does it not?
SpendixAI is built for personal and household tracking: Pro covers one personal workspace, and it is not a team, approvals or reimbursement tool. So it will not replace a team spend product. What it can do for one person is import their own bank or card statement as PDF, CSV or Excel, keep receipts with their transactions, and export a CSV. A freelancer who pays business costs personally could use that to see what they spent before claiming it back.
How do you stop the fallback from becoming permanent?
Set an end date for the temporary process before you start it. Say the tool was down on the 3rd and the sheet is used until the 7th, when finance enters everything and closes the sheet. A fallback that quietly continues for weeks splits your records across two places, and that is its own kind of mess. Tell the team the date it ends, and ask them to stop using the sheet after that day.
Questions to ask the vendor
- Is there a known incident, and what is the expected recovery time?
- Were any entries or receipts submitted just before the problem lost?
- Does the system keep an audit trail of what was submitted during the problem?
- Is there a supported way to enter items in bulk afterwards?
Useful ideas start with a clearer picture of your own spending.
Explore your reports


