Contact person: Business Client

Phone:Show

Email:Show

Location: Delhi, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a small but critical change in my Spring-based backend that runs on Project Reactor. Right now the billing fields in the shipment object ignore the profile preferences and fall back to our hard-coded defaults. Worse, the logic sometimes merges the account type (SENDER, RECIPIENT, THIRD_PARTY) from one profile with the account number from another, so invoices are going to the wrong payer.

What I want is straightforward: treat account type and account number as a single, inseparable pair. When [login to view URL]() indicates “overwrite”, replace both fields if either one is present in the preference; when it says “append”, leave both as-is unless the preference contains a full pair. Mimic the pattern already used in the codebase for the other overwrite/append fields so the implementation stays consistent.

The code is fully reactive—Mono, Flux, flatMap, etc.—so the fix must preserve non-blocking flow. Deliver an updated service class (and any helper classes you touch), plus unit tests that prove:

• Overwrite replaces both type and number together
• Append leaves both untouched unless a complete pair is supplied
• No cross-mixing of profiles under any combination of null or non-null inputs

I’ll run the tests in our pipeline; once they pass and the build stays green, we’re done." (client-provided description)