A few things keep coming up around Deel Advance so wanted to put clear answers in one place.

The eligibility system recently changed. It no longer works as a static checklist where green checks mean access. It now evaluates automatically based on recent account activity, and it reassesses daily.

Even if you've used Deel Advance before without any issues, access can temporarily pause based on four factors:

Payment consistency: how frequent and regular your incoming payments have been.

Limit usage: whether your previous advances approached your maximum limit.

Advance frequency: taking consecutive or back to back advances. The feature is designed for emergencies, not as a regular supplement to income.

Repayment history: the timing and completeness of past repayments.

One important thing Deel's platform states clearly: support cannot manually override or adjust eligibility. The system will automatically notify you when Deel Advance becomes available again. This means if you contact support and they say it's out of their hands, that's accurate, not a brush-off.

On repayment when you're between clients: if you're not receiving payments through Deel, the outstanding balance stays until funds flow through again, at which point it's automatically deducted. Deel no longer offers installment repayment plans.

On the advance input bug: some users are seeing the input field default to the full available amount with no option to enter a custom number. Contact support via live chat and ask them to process the custom amount manually while the bug is being fixed.

If you have a specific situation not covered here, drop it in the comments or DM us.

This one keeps coming up with Micro1 contractors specifically, so worth laying out plainly.

If you did a project a while back, lost access to that account, assumed it had gone inactive, and then signed up fresh for a new project under a different email, you're not the only one this has happened to. The issue is Deel's system sees two accounts under your name rather than one closed and one open, and that trips compliance during verification on the new account, even though you had zero intention of running two accounts at once. The fix isn't something you can do yourself from your side. Closing or merging the old account needs to go through internal review before it can happen, it's not a settings toggle you can flip. That review process takes time, and there isn't a way to skip it just by explaining the situation again.

What actually helps speed things along, reaching out with both email addresses on hand, the timeline of when the old account was created versus when you lost access, and being upfront that it wasn't intentional. Trying to just delete the old one yourself or ignoring the flag and hoping it resolves won't work, since the account sits blocked until someone actually reviews it. If you're in this exact spot, the move is to contact support directly with both emails rather than trying to work around it or opening yet another new account, since a third account would only make the review more complicated.

(Deel team here, this comes up more than you'd think, especially with people who've done project based work through Micro1 before.)

Short answer, yes. Having multiple contracts on Deel at once is common, especially for freelancers juggling a few clients. Each contract sits separately, and Deel doesn't notify one employer that you've got another contract running elsewhere. Your employer can only see their own contract with you, nothing about anything else you've got going on the platform.

What Deel doesn't do is check your contracts against each other. If one of them has an exclusivity clause or a restriction on outside work, that's between you and that employer, not something the platform enforces or flags. So having two contracts is fine on Deel's end, but whether it's fine on your end depends entirely on what you actually signed. Worth reading that clause again before assuming it's a non issue.

On the account itself, it belongs to you, not any employer. It's tied to your email. If you've only got one contract right now, the contracts page routes you straight there since there's nothing else to show, but add a second one and you'd get both listed instead. Losing a contract doesn't wipe the account either, your login and history stay put, only that specific contract goes inactive.

So the account is yours to keep across however many contracts you take on, the exclusivity risk is yours to manage.

Some users get their withdrawal returned with a message saying Deel detected a VPN, proxy, or IP masking software, even when they weren't using any. This is a false positive from the automated fraud detection system, not an indication that anything is wrong with your account or your withdrawal method.

Why it happens: certain ISP routing paths, mobile networks, and shared network infrastructure can look like proxy traffic to automated detection systems. This is especially common in some regions where internet traffic routes through shared nodes. It's a technical limitation, not a flag against your account.

What actually fixes it:

Clear your browser cache and try a different browser. Switch between WiFi and mobile data before retrying. Some people also resolve it by trying from the Deel mobile app instead of the web browser.

If the retry also fails, open a live chat in the Deel app and ask the support team to manually review and clear the automated flag on your account. They can bypass it once they confirm you're not actually using a VPN. This is not something you can resolve by waiting, it requires a support action.

What doesn't help: waiting, retrying with the same setup, or submitting another support ticket without specifically asking for the flag to be cleared manually.

If you're stuck in this loop, DM us with your account email and we'll make sure it gets to the right team.

Esto aparece mucho en el sub y no siempre hay una respuesta clara, así que lo resumo desde mi experiencia.

Si trabajás para una empresa extranjera y recibís pagos en USD (por Deel, Wise, transferencia directa, lo que sea), en Chile eso se llama renta de fuente extranjera y sí hay que declararla.

Cómo funciona la declaración:

En el Formulario 22 del SII, que se presenta una vez al año, existe una sección para rentas del exterior. Ahí vas a declarar el total de lo que recibiste durante el año, convertido a pesos usando el tipo de cambio del dólar observado del Banco Central al momento de cada pago. No hay un umbral mínimo para declarar, cualquier monto de fuente extranjera entra.

Si estás en segunda categoría o como independiente, el tratamiento puede variar levemente, por eso vale la pena hablar con un contador que entienda el flujo de ingresos del exterior.

Qué hacer con los USD antes de declararlos:

Wise es lo que usa la mayoría. Deel no cobra comisión por retirar ahí, la tasa de conversión a pesos es mucho mejor que la del banco, y podés mantener el saldo en USD hasta que necesites pesos. También podés abrir una cuenta en USD en Banka o algunos bancos locales si querés que el dinero entre directamente a la banca tradicional.

Para el registro:

Guardá todos los comprobantes de pago. Deel los tiene disponibles en la plataforma bajo cada transacción. Eso es lo que vas a necesitar para sustentar los montos declarados.

Si alguien tiene experiencia específica con Inicio de Actividades en el SII para este tipo de trabajo remoto, sirve mucho compartirlo en los comentarios.

We've encountered this pattern often enough that it's useful to address it clearly. Typically, a company signs with an EOR, includes a two-week onboarding timeline in the contract, hires a candidate, sets a start date, and then the EOR misses that deadline. The usual explanation is something like "the local partner in that country is still processing."

However, this explanation indicates a key issue that should have been clarified before signing. If the EOR relies on a local partner, the two-week timeline wasn't entirely within their control; the partner has their own queues, document processing, and response times. The EOR can escalate issues but cannot physically intervene in the local office. To avoid surprises, ask directly whether they own the legal entity in the country you're hiring in or if they route through a local partner. If they use a partner, ask for its identity. Providers owning local entities can give clear answers immediately, while those using partners often hedge, say "it depends," or promise to follow up, either because they lack information or prefer not to disclose it.

This also explains why quotes for the same country can vary significantly: providers owning their own entity bear the full infrastructural costs, while those using local partners may be adding a margin that skews prices. It's wise to ask about this before signing, as their answer reveals more than their SLA.

(Deel team here, we own our entities in every country and can verify this upon request. Happy to confirm for any specific market in the comments.)

A few things keep coming up around Deel Advance so wanted to put clear answers in one place.

On eligibility changing unexpectedly: the system evaluates daily and responds to both account-level factors and broader conditions. Even when the visible checklist shows all green, backend signals can affect eligibility in ways that aren't surfaced in the checklist. If everything looks fine but advance is still unavailable across multiple cycles, that needs a manual review, not a daily recheck. DM us and we'll escalate.

On repayment when you're between clients: if you're not currently receiving payments through Deel, the advance balance stays outstanding until funds flow through your account again, at which point it's deducted automatically. Deel no longer offers installment repayment plans. If you're in a hardship situation, the best thing to do is stay in contact with the Credit Risk team and communicate proactively rather than going silent.

On the advance input bug: some users are seeing the input field default to the full available amount with no option to enter a custom number. If this happens, contact support via live chat and reference the bug specifically. They can process a custom amount manually while it's being fixed.

If you have a specific situation not covered here, drop it in the comments or DM us.

(Deel team here.)

We've seen quite a few people getting stuck in the same loop lately: they switch phones, lose access to their authenticator app, and then discover that the standard support routes aren't working either. The Cal link throws a 404, the email support form doesn't send, and support@deel.com bounces back with an autoresponder.

If this is happening to you, here's the actual path out.

The video call route at app.deel.com/contact-support/video-call is the one that works for account access issues where you can't log in. It runs 24/7 and is specifically designed for situations where you can't get into your account. They verify your identity on the call without requiring you to be logged in first.

Before you jump on that call, go back to the login screen and look carefully around where it asks for the authenticator code. There's sometimes a link for "try a different verification method" or "send OTP via email" tucked in there. Easy to miss. That said, if your company admin has set 2FA as mandatory for your account type, email OTP won't be available as a fallback.

One thing we want to be upfront about: the Cal link has been broken for some users and the email support form has had issues too. We're aware of it. If the video call route also fails, DM us directly with your account email and we'll get the right team to manually restore your access.

(Deel team here.)

Landing somewhere new and getting locked out of your own money is one of those things that never feels real until it happens to you. You try to pay for coffee or check your balance, and suddenly there's a fraud alert, or a verification code that never arrives because your usual number doesn't work there anymore. It's almost never the big transfers that trigger this; it's the small stuff: a card flagged for an unfamiliar location or a login text sent to a phone sitting in airplane mode.

A few things actually cut down how often this happens.

- Telling your bank or card provider before you travel still works, even though it feels old-fashioned, because many fraud systems automatically flag unexpected countries.
- Setting up a second way to get a login code matters too; an authenticator app instead of a text message means you're not depending on a phone number that only works in one country.
- Keeping a small backup source of money, a second card from a different provider, or a bit of cash in the local currency means one blocked card doesn't leave you fully stuck. And checking whether your bank has travel notifications built into their app saves you from having to call anyone at all.

What doesn't help much is assuming it won't happen because you've traveled before without issues. Fraud systems become more sensitive the more countries appear on an account within a short window, so a pattern that used to work can stop working without warning.

Anyone else have a story about getting locked out of your own money at the worst possible time, and what actually got you back in?

Deel team here; we hear versions of this more often than you'd think.

UK closed-year FPS is its own workflow. Germany the social security side is genuinely terrifying because of director liability. France the majorations stack up fast once you miss droit à l'erreur on the next DSN.

At what point does it go from fixing it on the next filing to needing the local accountant involved before you touch anything?

Is there an escalation rule, or is it case by case?

Germany's biggest 4-day workweek trial just wrapped (45 companies, 13 industries, 6 months), and 73 percent of the companies kept it permanently. Productivity even went up 1 to 3 percent in some of them. Mexico is pushing legislation towards shorter workweeks. HBR ran a piece in April basically asking why this isn't the default yet.

And between 1900 and 1970, the workweek in most of Europe dropped from around 60 hours to 40. Each generation just worked less than the one before. Then it stalled. We've been stuck at 40 for over 50 years now (which is wild when you think about it).

So, when our kids hit 30, are they on a 4-day default?

Does the historical pattern of every generation working a bit less just resume after a long pause?

Or have we hit some kind of structural floor where productivity gains stop translating into time off, and the 5-day stays put for another century?