Skip to content

ON Feedback - 2025-10-02

TL;DR

Core file upload flow works - Palm recognized columns, categories, and accounts. Issues surfaced around column limits in mapping UI, European number formatting, and inability to edit saved mappings. BigQuery identified as ideal integration source for AP/AR (bypassing Kyriba).

Overall Sentiment
Direction validated Yes
Stage shown Bicycle
Ready for next stage Needs fixes first
Blocker for them? No - workarounds exist

Source

  • Transcript: 2025-10-02-batch-uploads-testing.md
  • Date: 2025-10-02
  • Participants: Amanda Mitt (Treasury Analyst), Federico Morando (Treasury Intern)
  • Context: Live testing session uploading tax payment files

This Iteration: Validation

What they validated about the current design:

  • AI column recognition works - "it recognized the events... that's good"
  • Category mapping works - Palm correctly mapped their budget codes to Palm categories
  • Multi-sheet handling - Palm recognized data from first sheet automatically
  • Duplicate detection - Acknowledged as useful for re-uploading files

Important Nuances

  • They're okay with making file format changes on their side if needed
  • Weekly upload frequency means manual adjustments are acceptable
  • Tax and talent files are the priority for file uploads; AP/AR should go via BigQuery

Future Iterations: Suggestions

High Value

  • Edit saved column mappings - Currently locked after first upload. "We are going to release so that you can change this."
  • European number formatting - Comma notation (1.000,00) not recognized. "We'll look into that."

Medium Value

  • Column limit in mapping UI - Couldn't scroll to see all columns. Need to investigate if UI issue or hard limit.
  • Google Sheets integration - "For tax and talent, yes" - direct connection to Google Sheets

Longer Term

  • BigQuery direct integration - "Palm could be here instead of Kyriba" - bypass Kyriba's daily delete behavior entirely

Questions Asked

  • Due date vs AP payment date → Due date is forward-looking; payment date is filled after the fact
  • How does Palm handle stale data? → Past dates not included in forecast, saved for variance analysis
  • Column limit in mapping? → Need to check with engineering

Raw Feedback Quotes

"It recognized the events... that's good." - Federico (on AI column recognition)

"We can adjust to that obviously." - Federico (on making file format changes)

"My ambition here is actually to make it easy for you guys." - Emma

"We don't really feel like I would really think about [manual work]... once a week would be fine." - Amanda

"Palm could be here instead of Kyriba." - Amanda (on BigQuery integration)

"Don't be afraid to do this feedback and say oh we would prefer [something different]." - Emma

Action Items

  • [ ] Check column limit issue with engineering (UI scrolling or hard limit?)
  • [ ] Support European number formatting (comma as decimal separator)
  • [ ] Enable editing of saved column mappings
  • [ ] Discuss BigQuery integration approach in Berlin visit