why is WBS not matching credit card transactions t...
# ask-stanley-ai
a
why is WBS not matching credit card transactions to actuals even though it includes the right activity code on the expense line
c
AI generated answer (using internal Slack threads):
Based on the conversations provided, the issue of WBS not matching credit card transactions to actuals even though it includes the right activity code on the expense line could be due to several reasons: 1. Memo Mismatch: The memo on the credit card charges might not be matching with the memo on the expense reports. The memo on the credit card charges is usually the memo in the credit card transaction header, whereas the memo on expense reports is the line item detail memo. If there is a mismatch between these two, it could lead to issues in reconciliation. 2. Newline Character in Memo: There could be a newline character at the end of every memo added by the bank feeds suiteapp. This could make the memo match useless and lead to issues in reconciliation. 3. Lack of Project Tasks: If you are using project budgets and want to compare budgets to actuals, you would need project tasks. The budgets on projects can only be entered once a project schedule is added (i.e., project tasks). If you are using the normal financial budgets and using projects or segments in those, that works without project tasks. However, the project profitability reporting requires project budgets and tasks. 4. Manual Entry of Credit Card Transactions: If your accounting department is manually creating credit card transaction records that correspond to each expense report, there could be errors in data entry that lead to mismatches. Please review these points and see if any of them apply to your situation. If none of these seem to be the issue, there could be other factors at play that are not covered in the provided conversations. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.813711643
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.805600703
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.804238856
Please provide your feedback on this answer.