- Rating
- 2
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduced XBANK, an anonymized corpus of 91.5M daily-aggregated corporate-client transaction rows. built a nested benchmark examining aggregation changes and cross-bank transfer, and a dictionary-free schema-alignment protocol based on semi-relaxed Fused Gromov-Wasserstein optimization.
Critical strengths
- This paper introduced XBANK, an anonymized corpus of 91.5M daily-aggregated corporate-client transaction rows, which together with MBD forms the a pair of industrial-scale banking datasets with distinct schemas.
- Applied Fused Gromov-Wasserstein assignment to XBANK and MBD, and showed better performance than simple Hungarian-assignment column matcher.
Critical weaknesses
-
Banks may not be able to share data or models because of privacy and legal constraints. Even if they can, their customers may behave quite differently. The paper does not say whether XBANK and MBD cover overlapping customer populations, or explain why a representation learned from one should transfer to the other. If the datasets come from the same financial institution, why can’t they share feature names or a common schema? If they come from different institutions, how does the method deal with differences in their customers? How to make sure all the inputs needed from the frozen representation are available in the new dataset? Without a clearer account of the setting, it is hard to see the use case for XBANK or why these datasets are needed to test transfer learning.
-
The title frames the paper around transaction foundation models, but the paper does not explain why XBANK and MBD make a suitable benchmark for them. Nor is it clear that any of the five models evaluated are transaction foundation models. Applying FGW to the two datasets does not, on its own, seem like a strong methodological contribution. A public B2B transaction dataset is valuable, but the paper needs to say more clearly what XBANK makes possible for transfer learning or foundational model that existing datasets do not especially.
Questions for authors
- What is the intended use case for cross-bank transfer? What would each bank need to share in practice, and why is XBANK useful for studying that setting?
- Does the method assume that all features needed to compute the frozen representation are available in the new dataset? If so, how likely is that to hold across banks with different data collection practices and schemas? What happens when some features are missing?
- Do XBANK and MBD contain the same clients, or different client populations? If the populations differ, how does the approach handle differences in customer behavior? Could those differences cause the feature-matching step to fail?
- How were the combination weights in Section 5 hand-tuned? Were they chosen using a separate validation set or fixed before evaluating the reported results? It would help to show how sensitive the results are to these weights, to rule out cherry-picking.
- Can the authors explain the finding that aggregation shift does not uniformly degrade performance? Is there evidence that this result holds beyond the particular distributions in XBANK and MBD? If it's mainly due to the separate normalization, what should researchers take away from it when designing future methods or benchmarks?
- What makes this a benchmark for transaction foundation models specifically? How do the five evaluated models test the capabilities implied by that framing, rather than transfer learning?
2 comments
Thank you for providing the cross-bank transfer scenario. Could you provide real-world use cases or concrete examples that support its practical relevance? Given privacy concerns, even sharing a frozen, pretrained encoder between two banks may require additional privacy-preserving measures. This scenario may be more realistic in non-financial settings.
You state that “Unfilled fields are zero-filled, following the MBD adapter’s own absent-columns convention.” It would be helpful to quantify the impact of missing features on the approach’s performance.
The response does not address my earlier question: “If the populations differ, how does the approach handle differences in customer behavior? Could those differences cause the feature-matching step to fail?”
Overall, I appreciate the authors’ efforts to clarify these points. However, the concerns above remain unresolved, so I will maintain my original score.
Thank you for pushing on the practical setting and the foundation-model framing — both deserve a clearer account than the original submission gave.
You raise a fair question about the intended use case for cross-bank transfer, and why two banks would ever need this rather than simply sharing data. The setting we have in mind is deploying a frozen, pretrained transaction encoder at a bank that took no part in its pretraining. What actually crosses the institutional boundary is (1) the frozen model weights pretrained only on the public MBD corpus, and (2) column-level statistical summaries of the source bank's pretraining schema (cardinality, entropy, quantiles). The receiving bank runs the frozen encoder locally on its own data and trains its own lightweight downstream classifier (LightGBM/MLP) on its own labels. Two competing banks generally have no legal or commercial basis to exchange raw transaction data, but a published checkpoint and a column-level statistical description are comparatively low-risk to produce. XBANK matters for studying exactly this scenario because it is a second institution with its own schema and its own targets, released publicly alongside MBD, which makes the scenario testable by outside researchers, not only internally at a bank.
You ask whether the method assumes every feature needed for the frozen representation is available at the new institution. It is not. Section 5 explicitly handles the case where no admissible XBANK column exists for an MBD field — "if Aj=∅, Yj is left unfilled". This as an outcome of the matching step. Unfilled fields are zero-filled, following the MBD adapter's own absent-columns convention.
Do XBANK and MBD cover the same customer population? Both datasets consist exclusively of corporate clients — XBANK comprises roughly 378K clients "of a major commercial bank," and MBD is a separately published dataset covering roughly 1.5M clients — and the two come from different, unaffiliated institutions. Verifying customer-level overlap between two banks' corporate client bases is not something either institution can do or disclose. We'd also stress that the corporate segment is, in our view, the most commercially important one for studying cross-bank transfer: corporate clients carry disproportionate transaction volume and revenue relative to their numbers. The representation that transfers well here has practical value. This also answers the related question of why the two institutions don't simply share feature names or a common schema: XBANK and MBD are maintained independently by separate organizations with no coordinated schema design, which is precisely why a schema-alignment step is needed.
Regarding how the combination weights in Section 5 were chosen, and how sensitive the results are to them: in the updated manuscript, the passport-distance sub-weights use equal weighting (1/4 per categorical component, 1/3 per numeric component), but the FGW combination weight — which balances the passport (statistical-shape) term against the structural (within-bank) term — is no longer fixed a priori. We select it empirically: we intentionally inject noise into a held-out field with a known ground-truth correspondence, sweep α across its range, and measure the fraction of correctly restored field correspondences at each value (Appendix A2). The masked MBD-to-MBD recovery experiment (across raw-to-raw, daily-to-daily, and daily-to-raw settings) evaluated with the optimal α selected by this sweep.
Finally, to clarify what distinguishes this benchmark as one for transaction foundation models: all five architectures are pretrained once, purely self-supervised, on unlabeled transaction sequences, with no task-specific labels entering pretraining, and are then used strictly as frozen feature extractors (Section 4.4). The same frozen checkpoint is reused across four MBD targets, three XBANK targets, two aggregation levels, two independent institutions, and two downstream probe families (LightGBM, MLP), without the pretrained weights ever being touched again. That reuse — a single pretrained asset applied across many downstream tasks and domains without retraining — is the operational property a foundation model is meant to have, which is also why foundation model Chronos-2 fits naturally into the same comparison. This is what separates the setting from ordinary transfer learning: nothing is adapted to the target site. The benchmark's three stress tests (aggregation shift, institution shift, and schema shift without a dictionary) were chosen because they are the specific modes a reusable pretrained asset must survive.